90% of my issues with Jira is that it's slow as balls. That's it. It's a website that cannot maintain any acceptable performance on a development machine. This applies to both UI with dialogs that open painfully slowly, and requests that take forever to arrive _and then_ keep loading megabytes of crap.
My org configured the local Jira to look like an oldschool forum: no dynamically loading content (which also means I need to refresh for newest comments), links are really just plain links, and I need to manually write markup for proper comment formatting.
It's fast and works really well compared to the guest Jiras that we sometimes use for external projects. My only gripe is that Jira's markup language is pretty bad.
Their Cloud ToS forbids sharing performance information (section 3.3i), which in its most generous interpretation is meant to avoid the type of speculation in this thread. https://www.atlassian.com/legal/cloud-terms-of-service
The theme of both your comments is that if anything is a problem with Jira, it’s all the organization’s fault because they have set it up poorly.
I would suggest that it’s 100% Atlassian’s fault that their product is so frequently poorly set up. They’ve basically abandoned their responsibility to design a good product in the name of customizability.
It's not the network that's the bottleneck, but the Javascript-bloated mess of the frontend.
edit: That isn't to say that Jira and Confluence are the only offenders. They aren't even the worst. Slack/Teams/Rocket.Chat are all just as bad and make me consider switching to a career without computers on a regular basis.
That’s kind of my point; all the tech you list here doesn’t have horrible lag, and aren’t generally even close to so bad they’d make someone want to switch careers.
So if it’s not them…
That's a lot of denial. Have you considered that Atlassian knows that these are Fortune 100 companies with contracts that would make Larry Ellison weep and therefore slap them on their biggest instances because hardware cost is negligible (as well as having dedicated employees to fix specific problems for them), and that _maybe_ the same amount of work isn't done for <generic company paying default prices for Jira Cloud>
Maybe!
But I doubt it. I run engineering at a b2b SaaS and specifically dedicating resources the way you're describing is not something I'd consider at the level Atlassian is at, especially considering there are people like you lurking out there.
