Yeah.
The bad news is that I've never heard of a workplace that's managed to change that culture once it's set in. The good news is that there are plenty of places to work which don't have that nonsense - which you can work in, if you can find them; which, to be fair, is pretty difficult. That said, it's worth the effort.
That's one of the questions I ask potential employers - "Say I'd like to make a small change to the workflow, in order to meet an oversight requirement - for example, on a project I'm engineering - how would I go about doing so using your work tracking system? How many people would I need approval from to do so? Let's assume the effect is internal to my project and would require no other team to change how they work. Is that possible?"
The answer usually says a lot more about the prospective employer than any technical questions about their code-bases do - and those are generally easy to suss out with a quick inspection, and SCM log perusal, anyway.
Powerful tools are flexible enough to be used correctly by knowledgeable people and help people become knowledgeable. Badly designed tools are tools which don't help people become knowledgeable and don't prevent unknowledgeable people from harming themselves or others using them.
Atlassian tools, like JIRA, are almost always powerful and flexible -- capable of great good in the hands of knowledgeable people. However, they are not well designed tools, and so - the vast majority of JIRA installations and setups are just as broken as the orgs which install them and JIRA offers absolutely zero assistance or resistance to that brokenness.