undefined | Better HN

0 pointsda39a3ee3y ago0 comments

I think one of the biggest problems with Jira is that it's taken the approach of so many other "Enterprise" products made by talentless teams: they just add all functionality into the app that anyone ever asks for.

The result is that for some of the companies I've worked for, each team's tickets have different but very similar "workflows" using custom state labels. In some projects when I go to close a ticket, it offers me approximately 30 different semantics which which to close the ticket. These include things like both "Done", and "Completed". What the fuck is the difference between "Done" and "Completed"? I do not know or care whether it is Jira that has populated this dropdown with such embarrassingly unintelligent crap or my company: if the latter then Jira should have neither encouraged nor even made it possible.

0 comments

3 comments · 1 top-level

jamesfinlayson3y ago· 2 in thread

I've worked at a company that had Cancelled instead of Abandoned - so if you try and "cancel" a ticket you're given a model with two action buttons - Cancelled and Cancel: Cancelled cancels the ticket and Cancel cancels the modal.

xp843y ago

You’ve hit my Jira pet peeve, kinda - accepting the default of naming the transition the exact same as the state it goes to.

Transitions should be verbs. States should be adjectives.

So your transition should have been called “Cancel” so your modal would have had 2 cancel buttons :D

(Or yes, another term should have been picked!)

jamesfinlayson3y ago

Yes Cancel and Cancel would have made no sense, and I think that should have told someone that Cancelled is an awful state name.

j / k navigate · click thread line to collapse