Hacker News Reader

Comment by seattle_spring | Hacker News Reader

The irony of this comment being that managing JIRA tickets is probably the absolute biggest time-sink of any organization that uses it.

View on HN

I find JIRA light weight. The trick is not to follow too many processes. Drag on tickets to your board when you start them and move then through the swim lanes. The worst cases are when people set up too much security and complex transition rules so that people are blocked by JIRA.

JIRA ain't perfect though. The constant UX changes drive me nuts. At least HN still works the same way as 10 years ago, but JIRA keeps changing like a shapeshifter.

The fact that larger companies that use JIRA have to employ full time "JIRA Administrators", or worse, teams of JIRA admins, suggests that the tool is anything but lightweight.

Larger companies need meta-roles. That is never going away. If that "PMO" person isn't using JIRA, they are using something else, or there are even more people wasting time dealing with all this via email and shared Excel sheets.

Thankfully (and also regrettably) in the org I work in now we don't have a pr standard yet... But we do use jira some of our people commit with just the bug prefix and number and not at least the title.. I really don't want to have to go paste that into the jira URL (usually more than one) to see if what you think is the issue is really the issue... Having at least the description for what you fixed helps...

Maybe it's time to dust off the "go to hell hat" and start demanding more info from the submitter...

The complexity context has to end up somewhere (or nowhere). JIRA is a superior tool in comparison to commit message text.

And an industrial mining dump truck with 14 ft wheels is a superior tool to a cargo bicycle. Doesn't mean it's the right tool for the job.

Reply on news.ycombinator.com