Hacker News new | ask | show | jobs
by paulddraper 2819 days ago
JIRA Core is a good issue tracker.

However JIRA Agile is a dumpster fire, partly because JIRA Agile reinvents JIRA.

Summary field? Yes, but also "Epic Name" field.

Status field? Yes, but also "Epic Status" field.

Priority field? Yes, but also "Rank" field.

Subissues? Yes, but also "Epic Link" field.

And then boards and sprints are weird. Boards are supposed to be just views, but then access permissions for closing sprints depends on the view you were looking at when you created it.

Plus the UI bad; the whole board gets really squished and becomes essentially unusable if I half-screen it.

3 comments

My main gripe about JIRA, other than how abysmal it gets when you add a slew of custom fields and workflows all over the place, is that I can't sort on the boards based on all of these fields I've setup. I set priority and severity on every issue, yet I can't sort by those fields in the planner or board, that's infuriating to me.
Check out Jira cloud, you can filter with a single click in the Next-gen UI by issue ower, epic, or label, no JQL required.
Not talking about the search or search results, talking about the Active Sprint board and Backlog.
@TheGRS, that's what Rank is for. Boards are using Rank field for ordering, that's why you can drag and drop card up and down. Also that is the thing that allows a global order across multiple projects - you can have boards which span across very weird sets of issues thanks to JQL
I'll tell you a secret, there are no "subissues", there are only issue links and UI represents different kind of links differently ;-).
Subtask issuetypes are a real thing, and are different to issue links.

Different parts of the UI and some functionality works differently for subtasks than for linked issues.

For example, you can set it up so that you can't close a 'user story' until all subtasks under it have been closed. Not possible out of the box with linked issues.

I'll tell you another secret: Epic Link is something else entirely.
Yep, it's a custom field, purely Agile's feature.