Jira is a framework for building something which approximates your actual processes.
> Justin said “I wish Atlassian would sit down with real-world developers and design this product the way we need it to work.”
The way 'you' need it to work. The process 'you' use. I suppose it's possible to build a business on creating a completely bespoke ticketing system for each company which uses one. Over time, that business might gravitate towards building a general toolkit which can be configured for each use case...
Oh look! Jira!
I'd bet that everyone's got their own distinct idea of where subtasks, ticket relations, etc actually fit in their workflow.
The article clearly exists to sell LinearB's product, which will of course work great for people who have the specific problems LinearB are solving with their product.
The rest of us will configure Jira within epsilon of 'works', then spend an afternoon reading about APIs and bash out our own automation service to update X different management tools appropriately for our workflows, and then go down the pub to bitch about management.
JIRA is the most popular of all tools on the market, which are glorified gantt points across disparate fragmented views. This is an element of modern tech that makes large organizations hilariously inefficient.
I've used Jira for years and never understood the hate.
The only times I have had real problems have been with particular idiosyncratic configurations or conventions that someone at my end has put in.
The Jira UX is amongst the worst in the business.
And yet... there it is, on every workplace with an useless operations team.
P.S. Look at this discussion for example https://jira.atlassian.com/browse/JRASERVER-4446 , subtasks concept is hard.
This is an emblematic quote:
Behind the bombast, the author assumes that the purpose of subtasks is to provide micro-level insight on progress to PMs. I agree that this would be a misuse of subtasks. Speaking as an engineer, I _love_ subtasks because they help me keep track of my various efforts towards whatever feature the ticket is tracking. Also, I'm the one who defines them!Jira isn't anyone's favorite software, but it is so configurable that it ends up being an embodiment of your dev process. If you hate it, chances are it's because you hate how you're managed.