4 ms·
One trouble with JIRA is that it doesn't come opinionated, this often means that if one team starts tweaking it, another team gets presented with 30 fields and
by eterm 8y ago
One trouble with JIRA is that it doesn't come opinionated, this often means that if one team starts tweaking it, another team gets presented with 30 fields and no idea what to do with them all.
Or you get one location who try to use it while simulataneously another location might use it in a completely different way, and then it becomes even harder to really keep a grip on what's going on.
You also get fights over whether tickets should represent overall state (So they move from TODO/INPROG/DONE) or represent the next step needed (So they move from TODO/IN DEV/IN QA/TO DEPLOY) etc.
Or you try to do both of those and have a state explosion and no clear idea of actual throughput.
After using too many badly run JIRA instances I'd actually like a simpler system to come along and say this is how you use this tool, it's OK if you don't want to use it this way, there are other tools for that.
- jasonpeacock 8y agoThis is a JIRA management failure - why is the same workflow being imposed on different teams? Either the company has agreed that all teams will follow the same workflow, then you do as described above, or each team owns their own workflow definitions.
- cybrexalpha 8y ago>each team owns their own workflow definitions JIRA actively makes this hard. To modify a workflow a user has to be a Global JIRA Administrator. The whole design of JIRA is based around management. It's not really for developers, as much at is is for your boss. This explains why Atlassian can get away with the user experience being so bad - it doesn't matter because developers aren't the ones choosing it.
- mwarkentin 8y agoI think the “new” JIRA project is more self management focused. Of course it only supports a small subset of overall features right now.