What are the difficulties in working with Jira?

Question

Project management

We are working on a project management system for software developers (task tracker), respectively, we are studying the "pains" of users of such systems. Very interested in the opinion of users about Jira.
What challenges have you encountered while working with Jira? Were there any critical issues, unresolved pains that caused you to stop using Jira and choose another product? I understand that Jira is a cool system with great opportunities, but many still scold it and choose other solutions. Please share your opinion, what do you think is wrong with Jira?

Answer 1

1) Very frequent redesigns that change the entire UI
2) Crap with a time track (you need an estimate, the balance, spent) to beat with pens.
3) Related tickets are not made in the fastest way.
4) The Jira + TestRail bundle is not made in the easiest way.
This is in terms of a developer who works on tickets.

Answer 2

Three-level nesting of tasks is not supported, only plugins or crutches.
I am pm at the bank and we have our own history with the approval of applications for revision, budgets and other stories. That is, to make a story where business requirements are first sawn, then system analysis is sawn inside, and then a specific decomposition into technical tasks is already going on inside, we could not. We made a double nesting and a third one, where technical tasks are subtasks (sub-tasks), but immediately ran into another problem, subtasks are not visible on the boards and sprints cannot be formed on them, such as the authors themselves are fat against this.
These are specifically the pains and peculiarities of my direction, and we have 11 of them in the bank, and each has its own processes and workflow, and there were no more special problems with it. This is a very versatile product in which you can do whatever you want, it depends only on the hands of the admins.