Every few weeks someone at work will ask about some basic functionality missing from Jira and we just link this as an explanation: https://jira.atlassian.com/browse/JRA-9091

That's amazing. Soon there will be people using JIRA, waiting for a feature that was requested before they were born.

This comment thread is so funny to me because Jira is actually the least unpleasant of all the enterprise software I'm forced to use at my job (lots of Microsoft stuff) so by comparison it's actually fine.

When we were forced to start use Jira a year ago it was kinda maybe acceptable, but every week someone in the organization adds a new custom field to issues, so it's growing scarier than bugzilla...

Back when I used Jira I actually quite liked it. Not that it was the best thing out there, but honestly with a little bit of config we could set up our (mandated by law) process quite easily and follow it.

Speed isn't the best, but it was either that, use Redmine with a massive config or wrap the shop up.

Why is JIRA so slow?

My understanding is that JIRA was originally built as an on-premises solution, so request latency wasn't an issue.

Then they moved everything to a cloud hosted solution, but the assumption of requests being effectively zero latency was still built-in, so now firing hundreds of requests with high latency makes everything feel super sluggish.

I'm working on my own issue tracker [0] that stores everything locally, which means no network latency. Eventually I'd like to build a sync backend for it so you can share it with a team, but for now everything runs locally.

[0] https://twigtask.com/

Oh, that would explain why I had no problem with JIRA.

My company had paid for the locally hosted version of JIRA for security policy reasons.

We use an on prem Jira and it is still shit. Would not recommend at all.

Yeah, our on-prem Atlassian installation is utter crap performance wise, opening a Confluence page often takes 30 seconds or more. I also get pissed off every time we try to upgrade our SolidWorks installation because they share a DB server. Atlassian doesn't support the most recent versions of Microsoft SQL Server, but SolidWorks only supports the latest couple revisions of Microsoft SQL Server so every time it is a pain to ensure that both systems are compatible and my IT refuses to move SolidWorks to a new server.

I think the opposite, but yeah.

The cloud is the original code base and the on premise is a FORK! Can you believe it? It's not even the same code and the on premise solution is so far behind.

Because it's a SPA trying to make 200 requests to get a ticket...and I'm barely exaggerating.

JIRA is not doing the SPA cause any favours :P.

My rage builds even just trying to use the search bar on JIRA. Keys don't get captured and get registered as page hot keys, or some keys are registered and others aren't. Crazy, just give me a dumb static search bar if you're not going to make life better. /Rant

JIRA was not always an SPA and it was still slow back when it was multi page.