Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Atlassian Acquires StatusPage

techcrunch.com

Post reply on HN
Print view View original

71–80 of 132 posts

Re: Atlassian Acquires StatusPage

#71

Post by cdjk »

owenconti wrote: post #46
balls187 wrote: post #13

Earlier quoted context omitted.

Ouch. I know snark is generally frowned upon, but HipChat and hosted JIRA/Confluence downtimes have been serious issues for us.

Not limited to just those products, we have issues with BitBucket. One example: it can sometimes take > 5 mins to merge a PR.

How many open PRs do you have targeting the branch you're merging into it? We heard through the grapevine that there are serious performance problems if you have more than 60-80 or so.

The solution for us was to decline those old PRs.

Re: Atlassian Acquires StatusPage

#72

Post by matwood »

owenconti wrote: post #46
balls187 wrote: post #13

Earlier quoted context omitted.

Ouch. I know snark is generally frowned upon, but HipChat and hosted JIRA/Confluence downtimes have been serious issues for us.

Not limited to just those products, we have issues with BitBucket. One example: it can sometimes take > 5 mins to merge a PR.

Add the recent bitbucket change that broke TeamCity fetching repos for building.

Re: Atlassian Acquires StatusPage

#73

Post by driverdan »

thesis wrote: post #30
balls187 wrote: post #13

Earlier quoted context omitted.

Ouch. I know snark is generally frowned upon, but HipChat and hosted JIRA/Confluence downtimes have been serious issues for us.

We switched from Hipchat because of this.

We did too. After using HipChat for years the frequent downtime became more painful than the costs of switching to Slack.

Re: Atlassian Acquires StatusPage

#74

Post by HappyTypist »

cdjk wrote: post #71
owenconti wrote: post #46

Earlier quoted context omitted.

Not limited to just those products, we have issues with BitBucket. One example: it can sometimes take > 5 mins to merge a PR.

How many open PRs do you have targeting the branch you're merging into it? We heard through the grapevine that there are serious performance problems if you have more than 60-80 or so. The solution for us was to decline those old PRs.

That's concerning. We use GitHub with a monorepo and have 462 open PRa without issue.

Re: Atlassian Acquires StatusPage

#75

Post by rmdoss »

1_800_UNICORN wrote: post #55
rmdoss wrote: post #37

As a happy StatusPage user, I am worried about this acquisition. Been more and more frustrated with Atlassian and recently we had to move away from HipChat due to multiple issues (constant downtimes). What are the good alternatives to StatusPage?

Are you really going to ditch StatusPage that quickly? I'm not a huge Atlassian fan myself, but StatusPage is a great tool.

Not really, just looking for alternatives. Atlassian so far has been leaving a bad taste for us.

Re: Atlassian Acquires StatusPage

#76

Post by Aldo_MX »

1_800_UNICORN wrote: post #55
rmdoss wrote: post #37

As a happy StatusPage user, I am worried about this acquisition. Been more and more frustrated with Atlassian and recently we had to move away from HipChat due to multiple issues (constant downtimes). What are the good alternatives to StatusPage?

Are you really going to ditch StatusPage that quickly? I'm not a huge Atlassian fan myself, but StatusPage is a great tool.

It is good to know which alternatives exist, "just in case".

Re: Atlassian Acquires StatusPage

#77

Post by nisa »

fletchowns wrote: post #67
dantiberian wrote: post #20

This acquisition doesn't fill me with confidence for the future. StatusPage was a clean, simple, and intuitive service. Atlasssian's software is the opposite of clean, simple, and intuitive.

I use JIRA, Confluence, and BitBucket daily and I'm a big fan of all three. Yeah, there's some aspects of their products I don't like, but overall I'm very happy with Atlassian offerings.

I'm kind of got to be a Confluence Wiki Admin without prior notice and overall I would agree that they do a good job - but everything addon and macro related could get some clear and concise overhaul. I understand it's an ecosystem and there are lot's of clever and good ideas floating around but I'm never sure what can I use on my local confluence instance and what not... some documentation for newbie "idiot" developers is there.. and something for total professionals.. anything in between seems lacking. Luckily there is some stuff on bitbucket that you can analyse to get a grip on some ideas but it's neither intuitive nor easy.

TL;DR: Confluence besides their Cloud is kind of badly treated and documentation for modern and up to scratch immediate plugin development is mostly nonexistent.

Re: Atlassian Acquires StatusPage

#80

Post by stephen_g »

djsumdog wrote: post #11

I remember when I was doing a talk in Melbourne, another developer told me what he didn't like about Atlassian was that they essentially only had one product (was it Jira? or Confluence? can't remember) and almost everything else in their offering set; they bought from other people and re-engineered to fit into their product line. Having administered, Jira, Confluence and Bamboo servers (all with slightly different i…

Luckily they do seem to have put some effort into making the administration of each project more consistent (at least between Jira, Confluence and Bitbucket Server). I've definitely noticed that things are slowly becoming more similar each release (and they got a lot more consistant in the frontend last year too).
Post reply on HN