Earlier quoted context omitted.
But jira is only a tool right? Blaming Atlassian for a poorly led organization seems slightly misguided. At some project size, measured either by software complexity/interoperability or user base, you will need a tool to manage issues and tasks. What you're talking about is an organization where developers are not empowered - but even empowered developers need an issue tracker or a board of some description. A "manag…
A good tool cannot guarantee good results, but a bad tool can shape its user's behavior in bad ways. The same individual without that tool might have behaved differently. I have seen this in what I call design-by-ticket where all the why and how for a design decision, including design by committee meeting notes, get put in jira tickets.
However, the final part has nothing to do with jira IMO. You would have the same behavior in these organizations regardless of tool.
The dysfunction you describe goes way beyond a single or set of tools.