3 ms·
It’s infuriatingly slow for me. Is this a configuration thing? Are our teams doing something different? It seems to me that it’s slow on a number of levels. It
by iainmerrick 8y ago
It’s infuriatingly slow for me. Is this a configuration thing? Are our teams doing something different?
It seems to me that it’s slow on a number of levels. It just takes a long time to load each page, and on top of that, basic operations usually take far too many clicks. So I figured it was just a bad tool.
- itomato 8y agoCloud performance is poor. OOTB Server install isn't a silver bullet nor is Data center. It's a spawling Java app with hundreds of discrete components, aging plugin architecture and is susceptible to configuration creep.
- Cyclone_ 8y agoYeah running it on premise should be faster.
- perlgeek 8y agoThe more fields you configure, the slower it gets. (That seems to be my impression, at least).
- mxschumacher 8y agosame for me. ~7s load times on a 100 Mbs connection with a new macbook pro are a daily encounter.
- slider_thor 8y agoJira Cloud & Jira Server (on-premise) are two different beasts. I can speak for on-premise only. On my on-premise system which is located on the other coast of the country, a ticket loads in 1.5 ~ 2.5 seconds once your assets are cached at least once by your browser. Things I've seen that can adversely affect your speed: installing random plugins that are poorly written, integrations, having too many admins over-complicating the Jira configuration. Learn the keyboard shortcuts to speed up your basic operations.
- iainmerrick 8y ago1.5–2.5 seconds is slow. (Faster than I’m getting, though, I’ll give you that.)