I think this post speaks to a lot of the issues I see not just with JIRA, but with enterprise tools in general.
Instead of adopting a sound process, customers will take an overly complicated business process and make the tool conform to this process. And please note that in this cases how you manage your code workflow is, in fact, the business process.
Any tool will struggle - often it's the process that's cumbersome and not the tools.
Re:How Atlassian Built a $10B Growth Engine
by switchbak on Tuesday January 02, 2018 @01:31PM
(#16054040)
My main gripe with Atlassian products is the execution - the ideas behind the products are usually sound, it's just pretty clunky to use.
For me, I'd love to have a flexible-enough tool for small to medium sized orgs that encourages a modern lightweight process and discourages ad-hoc process sillyness. Sometimes having a tool gently encourage better practices among all participants is a useful thing.
I've seen one dev excited - the one who tested other tools and picked Jira because it checked off on all the "features" needed. It really did handle the arcane and complicated workflow we had. But besides that few liked it, though it was a mix of hating the slow and unresponsive UI and hating the arcane process.