[csours]

To paraphrase many of the comments here: Most of the problems that devs have with Jira are not problems with base Jira, but with the implementation and usage of Jira.

Jira is perfectly fine, just like ALM is perfectly fine, TFS (Azure Devops?) is perfectly fine, Trello is perfectly fine, etc...

The problems come from the implementation, and the implementation is reflective of the culture. Any work planning tool becomes a work tracking tool and any work tracking tool becomes a punishment tool (without careful and attentive work to stop this effect).

[hinkley]

It's not the fall that kills you, it's the sudden stop at the bottom.

It is perfectly reasonable to blame the agent of chaos for the chaos that results.

[csours]

ehh, but this is kind of like blaming the results on hitting concrete vs hitting a cornfield. Yes, you might have a slightly less bad time hitting the cornfield, but the height of the drop is the more determining factor.

[hinkley]

My point is that people love to let Atlassian off the hook. They set up the conditions for failure. You can't blame all of the consequences on the person who touches it last.

It's really the same class of externality that we used to blame Microsoft for. You can try to collect all the cash and all the fame and then blame stability and usability problems on third parties, but not everyone is going to buy it.

If you weren't pandering in the first place, you wouldn't have all that cash or fame. You knew what you were doing. Even if you don't want to say it out loud.