News for hackers. Stuff that matters.
Re:Atlassian files for IPO by icedchai on Monday November 09, 2015 @12:56PM (#10534554)
What do you think about Jira?
Re:Atlassian files for IPO by rdtsc on Monday November 09, 2015 @01:59PM (#10534998)
Not OP.

Unlike Github's mostly developer centric issue mechanism, Jira is more suited for organizations the would have a QA department, a security review, a more complicated release process (multiple phases of validation and testing) or that that just need a custom issue state machine.

It just so happens that those companies also have money to buy Jira licenses and Atlassian is brilliant for letting OSS project use it as well. So they get a foot in the door at multiple places in the industry.

If startup developers don't like it, oh well, there is enough money for them to be made in the Enterprise market.

(Also, I noticed that there is an interesting plugin market for it as well, once you have audience that paid so much to use it, they'll be willing to shell out a a few hundred more for say Slack integration or other such plugins).

Re:Atlassian files for IPO by Laaw on Monday November 09, 2015 @01:00PM (#10534580)
Not a huge fan of Confluence (just give me Markup, dammit), but Jira is simply the best at what it does.
Re:Atlassian files for IPO by icedchai on Monday November 09, 2015 @01:02PM (#10534598)
Pretty much all developers I know can't stand Jira. Management loves it though.
Re:Atlassian files for IPO by Laaw on Monday November 09, 2015 @01:26PM (#10534772)
Jira is a super flexible tool.

Sounds like all the developers you know hate how their bosses use tools. I happen to love how my team uses Jira.

Re:Atlassian files for IPO by LukeB_UK on Monday November 09, 2015 @01:29PM (#10534795)
I love Jira. You just have to have it set up for the people using it every day (developers)
Re:Atlassian files for IPO by Dirlewanger on Monday November 09, 2015 @01:11PM (#10534669)
Yup, JIRA is a power-manager's wet dream. Whatever way one can think of for adding "things" to a task (and how to classify them, and how to keep track of them...), Atlassian has probably thought of it. For a developer who just wants to keep the tool at a distance and only log into it to move their shit across the scrum board and promptly log back out, they better hope their scrum overlords have looked upon them kindly.
Re:Atlassian files for IPO by cowmix on Monday November 09, 2015 @01:25PM (#10534768)
Almost every time my company gets called in to do JIRA consulting the situation is this: Devs bring JIRA in.. JIRA gets popular.. things get out of control.

It is almost NEVER brought in by management.

Re:Atlassian files for IPO by icehawk219 on Monday November 09, 2015 @05:33PM (#10536326)
I used to be a dev who brought in JIRA because I like it out-of-the-box and it can grow with a team. But I always tell my manager to NOT TOUCH THE WORKFLOWS and to just let things grow organically as the needs of the team grow (or don't). And every time the moment they click around and see the workflow editor we ended up with some big, bloated, convoluted mess. I've been burned too many times, I no longer recommend JIRA to anyone.
Re:Atlassian files for IPO by alkonaut on Monday November 09, 2015 @04:46PM (#10536049)
In my opinion it's a range of management requests that give rise to the workflow, and devs hate managing workflows with email, notes ("When you are done implementing move the issue to the X column and send a message to the testers group that..."). So then devs bring in JIRA to do some automation. Now the tester person gets an email when the issue is moved to the testing phase. But once everything is in place, management will see the benefits, and the workflow will "evolve", especially if the teams grow. It's pretty natural.
Re:Atlassian files for IPO by daigoba66 on Monday November 09, 2015 @08:47PM (#10537108)
The trick is that Jira should be "owned" by the dev teams, not by management. Management shouldn't even have a login, except perhaps to submit bugs.

The only exception is if Jira is used for project management type stuff - those projects can and should be isolated from dev projects.

Re:Atlassian files for IPO by serge2k on Monday November 09, 2015 @01:29PM (#10534805)
As a dev, Jira is the best of a bad lot.
Re:Atlassian files for IPO by colinyoung on Monday November 09, 2015 @01:39PM (#10534854)
I'm one of these. PivotalTracker is the only thing I don't hate.
Re:Atlassian files for IPO by mdolon on Monday November 09, 2015 @03:35PM (#10535630)
I used to be a Pivotal guy before looking into JIRA again recently. They've made a lot of changes to their platform that really make it a pleasure to use, at least for my needs (development work with small teams). There is a bit of setup work but once you do that, it's smooth sailing.
Re:Atlassian files for IPO by jacques_chester on Monday November 09, 2015 @08:59PM (#10537145)
Pivotal Tracker is deliberately minimalist. I didn't really get it until I started working at Pivotal Labs.
Re:Atlassian files for IPO by mlindner on Monday November 09, 2015 @02:56PM (#10535378)
I hate Jira completely. It is terrible. Best system I've seen is Pivotal Tracker.
Re:Atlassian files for IPO by acidburnNSA on Monday November 09, 2015 @09:51PM (#10537325)
I started using FOSS Phabricator on a medium-sized team (~20) for private central git hosting, code review, issue tracking, project management, etc. We absolutely love it and I wonder how it compares to Confluence/JIRA.
Re:Atlassian files for IPO by caoilte on Monday November 09, 2015 @05:05PM (#10536158)
Jira 3 was an okay issue tracker. Jira 4 is a SLOOOW issue and a terrible agile planning tool.

Much happier with Trello and a zero bug policy.

Re:Atlassian files for IPO by Laaw on Monday November 09, 2015 @05:24PM (#10536273)
> zero bug policy.

Oh, why hadn't I thought of that...

Re:Atlassian files for IPO by Zigurd on Monday November 09, 2015 @04:52PM (#10536090)
Jira can do anything.

Up to you if that's a bug or a feature.

The interesting thing is that it is very often used for Agile project management. It's massive overkill for that. It has the feel of something that evolved from an issue-tracking system, because it existed before Agile and morphed into an Agile tool.