I used it (Jira) for a short period of time a while back. I seem to recall that it's performance was highly influenced by non-obvious JVM parameters, and bits of the system would stall or crash without a clear pattern until a bit of trial & error with parameters solved it. It wasn't very "turn key" and the out-of-the-box config were... less than ideal. This was for a single user (me) so it's not like there was a much of a resource crunch.

We have 'macros' in https://www.cloudsynth.com to create issues on the various issue systems (jira/github/etc) and it it is actually pretty impressive how slow JIRA is compared to the rest of them. It's like theres a sleep loop or something.

First, this clone looks very nice and worth trying if your workflow fits it.

If this tool is still needing some feature you want, Do you run JIRA cloud? Jira by no means is perfect. It's one of the few tools that can handle complexity.

I noticed a huge leap in JIRA speed in switching from cloud hosted Jira to self-hosting.

On Cloud, Atlassian is mischievous and aggressively optimizes and constrains the resources.

If you don't use Jira often enough on cloud, it will be slow. The more it is used, the faster it gets.

One way to speed up JIRA Cloud is to hit the urls regularly with a script, keeps them cached.