News for hackers. Stuff that matters.
Re:Atlassian Acquires StatusPage by dantiberian on Thursday July 14, 2016 @05:20PM (#12097253)
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.
Re:Atlassian Acquires StatusPage by r0m4n0 on Thursday July 14, 2016 @06:42PM (#12097753)
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 install or business workflow did a bad job?

I don’t think you say the same about other competitors right now… ServiceNow? HP SMS or ALM? ClearQuest? I’ve used those and if you consider Atlassian terrible, I’m not sure what words you would use to describe them…

Re:Atlassian Acquires StatusPage by lojack on Thursday July 14, 2016 @07:29PM (#12097971)
> 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.

Re:Atlassian Acquires StatusPage by gregmac on Thursday July 14, 2016 @08:44PM (#12098281)
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 tool, where well-intentioned control points get in the way of actually Getting Things Done, both from the perspective of not thinking through all the complex scenarios (what? I have to fill out 5 fields before I can close this as a duplicate??) and from not trusting your employees (don't worry, a jr. dev is not going to re-assign a fix version even though they can -- or at least, they won't do it twice).

Re:Atlassian Acquires StatusPage by ymerej on Thursday July 14, 2016 @10:27PM (#12098608)
For you, there is Github issues. Have fun, cowboy.
Re:Atlassian Acquires StatusPage by nilkn on Thursday July 14, 2016 @11:11PM (#12098735)
More seriously, there's FogBugz, which intentionally is not very customizable to avoid the issues the above poster was referring to.

In my experience, FogBugz is a little too limited, so I do prefer Jira, but only when used by competent people who understand that the customization should not get in the way of getting things done and it should not be used to institutionalize a lack of trust in employees.

Re:Atlassian Acquires StatusPage by voltagex_ on Thursday July 14, 2016 @11:28PM (#12098787)
Having used HP Quality Centre, JIRA and Team Foundation, I think your snark is unwarranted and there is a middle ground to be found between very basic issue tracking and something completely overbearing like QC.
Re:Atlassian Acquires StatusPage by glogla on Friday July 15, 2016 @06:34AM (#12099986)
It's been years and HPQC still gives me nightmares.
Re:Atlassian Acquires StatusPage by manyxcxi on Thursday July 14, 2016 @09:12PM (#12098388)
I think another thing people get wrong is before even using it they assume they've got to dive into a ton of custom workflows.

I've had some fairly large teams able to use JIRA without a single workflow customization (especially with Agile). We've added custom fields and such along the way for better reporting and such but there is definitely some mileage you can get out of the box with it.

Re:Atlassian Acquires StatusPage by jjcm on Thursday July 14, 2016 @10:48PM (#12098677)
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 by clappski on Friday July 15, 2016 @04:05AM (#12099512)
We use ServiceNow at work, and it's absolutely horrible. Introduces so much red tape even to do simple things like become an administrator on a virtual machine requested against your account .
Re:Atlassian Acquires StatusPage by fnord123 on Friday July 15, 2016 @05:59PM (#12104110)
How do companies end up with the Service Now cancer? Are their sales meetings just hooker and coke parties? I've used it at two different companies and I wondered how anyone could look at it and think 'ok let's buy into this pile of horse shit'. My cat could do a better job.
Re:Atlassian Acquires StatusPage by stuff4ben on Saturday July 16, 2016 @09:53AM (#12106315)
You obviously haven't seen Remedy.
Re:Atlassian Acquires StatusPage by darkstar999 on Thursday July 14, 2016 @07:26PM (#12097955)
> 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.

Re:Atlassian Acquires StatusPage by timv on Thursday July 14, 2016 @09:48PM (#12098495)
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.

Re:Atlassian Acquires StatusPage by kannonboy on Friday July 15, 2016 @02:43AM (#12099290)
Hi timv, Bitbucket engineer here. I'm not on the PM team, but to my knowledge we have no plans to discontinue Hg support. The Bitbucket repo population is roughly 90% Git and 10% Mercurial, but due to our scale that is still a freaking huge number of Hg repos. We also hired one of the core Mercurial contributors last year to ensure we continue to improve our offering for both DVCSs. Of course I can't personally guarantee anything, but if I were an Hg user, I'd feel pretty confident that Bitbucket's support isn't going anywhere in the foreseeable future.
Re:Atlassian Acquires StatusPage by kannonboy on Tuesday July 26, 2016 @06:37PM (#12169257)
In fact, we just launched Hg support for Bitbucket's built-in CI/CD, Bitbucket Pipelines:

https://blog.bitbucket.org/2016/07/26/bitbucket-pipelines-be...

Re:Atlassian Acquires StatusPage by brianwawok on Thursday July 14, 2016 @10:58PM (#12098704)
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 by pseudalopex on Friday July 15, 2016 @09:10PM (#12104756)
Apparently Mercurial still accounts for 10% of BitBucket repos. That could be a profitable niche for a smaller company.

Also, most of the projects I've seen switch to Git have moved to GitHub. Partly network effects, partly Atlassian.

Re:Atlassian Acquires StatusPage by yeukhon on Thursday July 14, 2016 @10:54PM (#12098689)
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.
[dead]
Re:Atlassian Acquires StatusPage by amazingman on Friday July 15, 2016 @01:01AM (#12099024)
What was your intent when choosing to write this comment and then choosing to publish it?
Re:Atlassian Acquires StatusPage by vadym909 on Friday July 15, 2016 @12:39AM (#12098970)
Could it be that golf uses the term because par means equal. Its a pretty common phrase and means the same as 'not at par', 'up to snuff','not at the same level'. I've especially seen it used in hiring (high bar, below the bar, not at the bar'. Probably comes from the high jumper's bar.
Re:Atlassian Acquires StatusPage by fletchowns on Thursday July 14, 2016 @06:58PM (#12097825)
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.
Re:Atlassian Acquires StatusPage by nisa on Thursday July 14, 2016 @08:06PM (#12098161)
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 by jon-wood on Friday July 15, 2016 @03:53AM (#12099476)
So do I, and they're all tools that get the job done, but without any finesse or real care.

Bitbucket is inferior in every way go Github, with a UI that screams feature box ticking. Confluence is a place for documentation to go and die a slow death, and I'm still convinced Jira was entirely designed to keep project managers and mouse manufacturers in business - you can't do anything without fifteen clicks around the screen.

Give me Github, a repository full of markdown files, and Trello any day of the week.

Re:Atlassian Acquires StatusPage by eeeeeeeeeeeee on Thursday July 14, 2016 @06:14PM (#12097592)
When I saw the quote by the StatusPage founders saying they were aligned with Atlassian, I laughed. These companies are near polar opposites.
Re:Atlassian Acquires StatusPage by atwebb on Friday July 15, 2016 @11:18AM (#12101584)
Disagree on the Atlassian, well, JIRA at least. Just had to introduce it to a new group, we got cut short on the initial intro so I didn't get through much. Then to my surprise they were off and running the next day, they just got it.