It’s all due to local configuration, some IT kiddo sees all these bells and whistles and levers to pull, so they turn them all on thinking more features is better.
In the meantime the most efficient workflow I have has six states (planning, execution, UAT, deployment, warranty, closed) and it works just fine and stays out of my way.
I think the problem with JIRA is they don't really have a sane default install, it really feels like a bag of parts and then you assemble it. Maybe 2 or 3 opinionated templates that take a process end to end would help people, that just want to get started and that stare into the configurable abyss of JIRA and go "nope just want a ticket system".
Maybe the user experience can be good if the org is big enough to have 2-3 people managing JIRA full time but I'd hate to be one of those 2-3 people.
The Dashboard within Jira that we created has been really great as I have been using it along the charts it produces to communicate with my business partners. The data that we collect isn't perfect, but its good enough to construct a narrative that my business partners can grok. I have most recently used this information to help in successful pitch for a strategic re-design of our systems as well as an ambitious resourcing proposal to go along with it. Knowing how much of your time is lost to overhead allows me to plan ahead and justify the people that I need to make the redesign happen.
Jira having an API has been a real boon too. Personally I have used it with Python to mine for additional data that I need in reporting where the Jira dashboard is insufficient. I have also had my team's dedicate DevOps engineer drive all sorts of integrated work flow automation to ease the development process. My team operates within a large bureaucratic organization, so having the capability to automate all the artifacts for compliance has been a real time savings.
The integration with Confluence is awesome. It really makes managing my teams work so much easier. I love to collect meeting feedback notes in confluence and then tag the bullet points with Jira tasks that I create as follow up work. The Jira issue tables driven by JQL (Jiras Issue Query Language) are super useful when I need to create project plans that combine a mixture of content. I love just dropping in a list of all the tickets that we have outstanding.
I would not be nearly as effective w/o the combination of both tools.
JIRA does have a few technical failings. As you pointed out, its performance can be a problem. Additionally, as a normal user, I find its search lacking. If I want to find the story I worked on 6 months ago that involved adding middle name to the user table, I'm better off hunting through my commit log or my notes than using JIRA search.
There's definitely problems with it (its performance can be awful and require dedicated server clusters to keep it up at larger orgs), but come on let's be honest, it's a huge success story and lets orgs do things "their way" with project management and software development.