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

91–100 of 132 posts

Re: Atlassian Acquires StatusPage

#91

Post by m_mueller »

tajen wrote: post #50
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…

Their biggest product is JIRA followed by Confluence. Let's look at acquisitions vs internal developments: - 2003: JIRA - In-house - ~2004: Confluence - In-house - ~2007: Fisheye, Crucible (code analysis) - Acquisition - ~2008: Bamboo (builds) - Acquisition - 2010: Bitbucket - Acquisition - 2011: SourceTree - Acquisition - ~2012: Bonfire (JIRA Capture - screencast bugcatcher) - In-house - ~2013: HipChat - Acquisition…

You can add Allinea in there somehwere as Acquisition. Specialized in debugging of parallel code including GPU support.

Re: Atlassian Acquires StatusPage

#92

Post by cyberferret »

cyberferret wrote: post #54
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?

We use Cachet[1], an open source alternative. We checked out many status page services out there, but found it hard to understand how some of them (web apps with a handful of pages) were more expensive than our accounting system or project management services we subscribe to?!? [1] - https://cachethq.io/

For those interested - I just blogged about how we set this up here: http://devan.blaze.com.au/blog/2016/7/15/building-a-status-p...

Re: Atlassian Acquires StatusPage

#93

Post by ymerej »

gregmac wrote: post #81
lojack wrote: post #70

Earlier quoted context omitted.

> Maybe the admin that setup your install or business workflow did a bad job? I think this is key. There's so much customization allowed that its easy to get wrong. Your experiences can vary drastically between a well configured instance and a poorly configured one.

I'll also add it's not always obviously wrong when it's setup. For example, of course only QA people can use "Testing passed" transition. Of course there should be x, y, z fields filled out to be able to create the ticket. Well we're at it, let's make sure only the product manager can close a ticket with 'wontfix', and only the release manager can change a fixversion. This is a really common problem with any workflow…

For you, there is Github issues. Have fun, cowboy.

Re: Atlassian Acquires StatusPage

#94

Post by logicallee »

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?

>What are the good alternatives to StatusPage?

http://i.imgur.com/adl7Yc3.png

Re: Atlassian Acquires StatusPage

#96

Post by jjcm »

lojack wrote: post #70
r0m4n0 wrote: post #59

Earlier quoted context omitted.

Having used many different bug tracking, help desk, and ticketing softwares… Atlassian does a dam good job. Totally customizable screens, fields, and workflows with a modern UI. A decent webservice API I’ve integrated a few external tools into without much difficulty. I’ve also written a few gadgets and plugins and received a decent amount of attention through their plugin marketplace. Maybe the admin that setup your…

> Maybe the admin that setup your install or business workflow did a bad job? I think this is key. There's so much customization allowed that its easy to get wrong. Your experiences can vary drastically between a well configured instance and a poorly configured one.

That's one of the reasons why we're switching to a cloud model in addition to the self-hosted server model. Some people wanted an easier more straight forward experience.

Re: Atlassian Acquires StatusPage

#97

Post by ElliotH »

jroseattle wrote: post #22

"Adding a service like StatusPage, which launched three years ago, seems like a natural fit for Atlassian." Why is this a natural fit for Atlassian? Not being snarky, I just don't see how this is any more a natural fit for Atlassian than lots of other companies that provide picks-and-shovels to the software builders of the world.

One problem with the stack right now is if you are using Jira to track issues internally then users who aren't party to the ticket aren't able to see what's going on very easily. Perhaps/hopefully this will provide that sort of ongoing progress report, so if the database goes down there aren't 50 support tickets.

Re: Atlassian Acquires StatusPage

#98

Post by yeukhon »

timv wrote: post #86
darkstar999 wrote: post #69

Earlier quoted context omitted.

> In their official announcement today, the StatusPage co-founders also note that when the team explored the acquisition, “we were aligned on three important things: our complementary cultures, our desire to offer StatusPage as a standalone product, and our shared vision of the future of software.” Standalone product. I think it will be safe.

Bitbucket has remained a standalone product, but I don't think many of its original mercurial userbase feel like it's been "safe". When Atlassian bought bitbucket it was the place to host mercurial repositories. Now it's a git hosting service that hasn't gotten around to turning off mercurial support yet.

It would be a terrible move to disable mercurial support since Bitbucket is pretty much the only place you can host your Hg repo remotely with reputation. Other competitors just aren't up to bar.

Re: Atlassian Acquires StatusPage

#99

Post by brianwawok »

timv wrote: post #86
darkstar999 wrote: post #69

Earlier quoted context omitted.

> In their official announcement today, the StatusPage co-founders also note that when the team explored the acquisition, “we were aligned on three important things: our complementary cultures, our desire to offer StatusPage as a standalone product, and our shared vision of the future of software.” Standalone product. I think it will be safe.

Bitbucket has remained a standalone product, but I don't think many of its original mercurial userbase feel like it's been "safe". When Atlassian bought bitbucket it was the place to host mercurial repositories. Now it's a git hosting service that hasn't gotten around to turning off mercurial support yet.

Is that Atlasian or the general decline of HG? I havent installed HG in a few years now, and i am seeing the big projects still on HG switching to git.

Re: Atlassian Acquires StatusPage

#100

Post by brianwawok »

jroseattle wrote: post #22

"Adding a service like StatusPage, which launched three years ago, seems like a natural fit for Atlassian." Why is this a natural fit for Atlassian? Not being snarky, I just don't see how this is any more a natural fit for Atlassian than lots of other companies that provide picks-and-shovels to the software builders of the world.

Jira goes down a lot. Maybe it helps you notice faster?
Post reply on HN