4 ms·
There's good things about JIRA, and of course it needs to be configured and managed effectively to work for an organization. But it's so hard to configure consi
by johnwalkr 6y ago
There's good things about JIRA, and of course it needs to be configured and managed effectively to work for an organization. But it's so hard to configure consistently, and almost impossible to make it both flexible for various teams and have any sort of consistency across the organization. It's just so hard to manage. It's like Windows 10, in that there are at least 2 different interfaces to configure most things, and you just never build up the muscle memory to navigate to the right place. But it's even worse, because there's projects, issue types, issue state, swim lanes, form configuration and more, and it's a subjective decision to decide which of those are appropriate ways to configure. My mental model of JIRA is like 5 or 6 dimensions. Bitbucket integration is good, but god help you if you also use crucible and confluence which are good on their own but add more dimensions to your particular configuration of knowledge storage.
Maybe the user experience can be good if the org is big enough to have 2-3 people managing JIRA full time but I'd hate to be one of those 2-3 people.