The most annoying thing on a daily basis for me with JIRA is how slow it is. It seems like a cloud hosted one and a self hosted one are are equally slow. By slow I don't mean abysmally slow, but every action typically takes 500-750 ms. And if you use it regularly, that makes doing stuff a chore.

> The most annoying thing on a daily basis for me with JIRA is how slow it is.

I can't comment on the cloud offering, but I agree that the performance and resource consumption of the self hosted Jira is not great either.

To me it is not quite slow enough to negatively offset its usefulness. Perhaps I am also too used to working with even slower web applications to really take note of anything < 1s ;)

Again, to double down on my previous point: where it can get very slow very fast, is for ill configured systems... i.e. when running unnecessary permission checks on very large groups.

The 300+ mb page load to see one sentence of text on an issue is a big factor.

Surely 750ms is already in the absurdly slow category?

In general UIs should always respond in 100ms or less. For lord's sake GMail takes a full 3s which is slower than any desktop client took in 2000. Somehow people think it is okay to make your page slower because "ooh aah AJAX" and "oh I can just add a spinner" or something ...

Back when I used pine it just loaded instantly! No spinner, no splash screen, no progress bar needed.

And don't give me that "oh but it's in the cloud" crap -- the cloud isn't an excuse to be slow when I have a 300mbps downlink with sub-10ms ping times to headquarters and datacenters of these companies.

If you're used to fast paced web apps like Trello, yes.

It begs the question what could it possibly be doing to take half a second of wall time. That’s an eternity for a modern computer.

So it's not just me. I never used it professionally, but a handful of open source projects decided to use it. It felt like a slow, convoluted process to just open a bug report.

What about it caused this feeling?

Creating a bug report with Jira can be as simple as filling in a summary and a (optional) description, then click submit. If you use issue collectors, you may not even need an account in the system or directly access the Jira application to report the issue.

When each click takes 500-1000ms to respond, it doesn't matter how simple the workflow is.

The choice is to adopt a crap product like Jira and use it to model your existing flows or buy an SAP or NetSuite product and have it govern your business.