In our case though, we only have about 50 engineers and a few hundred thousand issues. Jira has performance issues in the 500 engineer / 100mm+ issue space - or it used to, perhaps they've resolved those issues by now.
In our case though, we only have about 50 engineers and a few hundred thousand issues. Jira has performance issues in the 500 engineer / 100mm+ issue space - or it used to, perhaps they've resolved those issues by now.
I would have gladly paid more for faster speed but it turned out the APIs were blazing fast and it was the JS that was slow. Not sure how we have had such different experiences. Seems impossible that your JS was executed that much faster than mine. I was using chrome FWIW.
If your software encounters idiots all day long, you’re the idiot.
THE main problem with JIRA is people breaking it with customization in one way or another.
Or put is on very slow, high network latency servers...
EDIT: Just to be clear, JIRA is never fast. But can be usable if you are not super sensitive to small latency.
Really, why wouldn’t you blame the maker of the bed?
If you make a tool that encourages Rube Goldberg machines, then you made something far worse than a Rube Goldberg machine; you built a device to construct them.
Our JIRA instance would lag while typing in the description box. You have to wait a second or two for it to catch up after typing a sentence. It was absolutely unusable.
My old x260 was not able to run jira/gcp/slack at a reasonable speed due to javascript performance :(