4 ms·

Jira has always been very quick and responsive for me. It offers a good amount of customization too, we have a custom workflow that makes sense for how we devel

Jira has always been very quick and responsive for me. It offers a good amount of customization too, we have a custom workflow that makes sense for how we develop software. I've never felt that jira has been a limiting factor of what the teams I've been on have wanted to do with our workflow. Never once encountered a major bug in it either.

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 ago
  Cloud 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 ago
    Yeah running it on premise should be faster.
- perlgeek 8y ago
  The more fields you configure, the slower it gets. (That seems to be my impression, at least).
- mxschumacher 8y ago
  same for me. ~7s load times on a 100 Mbs connection with a new macbook pro are a daily encounter.
- slider_thor 8y ago
  Jira 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 ago
    1.5–2.5 seconds is slow. (Faster than I’m getting, though, I’ll give you that.)
tachang 8y ago
What are you doing that I am not? Jira is slow as hell and updating statuses take forever. Are you on an onprem version?
- achamayou 8y ago
  I’ve used two separate onprem versions, and they were slower than hosted if anything.
- Cyclone_ 8y ago
  Yeah it's onprem
sergiotapia 8y ago
I also liked my time working with JIRA tools, however these days I've moved on to Clickup. https://clickup.com/ https://clickup.com/ It's like they spent much more time refining the UX and feel of moving around clicking on things. It's pretty great.
- lugg 8y ago
  > It's like they spent much more time refining the UX and feel of moving around clicking on things. I just gave it a whirl - for an hour or so - so take this with a grain of salt. Looks much nicer, and there definately has been more effort put into the design compared to trello / jira. Thats about where things end for me though. I don't think the UX is refined at all, it's full of usability faux pas and their CSS could undergo some basic usability testing as well. Jira's usability isn't that bad if you use sane defaults and avoid overconfiguration. Jiras main problem (and its a big fucking problem) is responsiveness. I did have a look at their suggestion forum and it looks very active I think I'll give them another look in a few months to see if they've managed to reign in some of the BS or if it only gets worse. (I suspect the latter will occur for various reasons.) And please, don't take this harsh critique the wrong way, if I was choosing a platform today I'd probably pick them, beauty is a hell of a drug - just don't confuse a nice looking design with UX.

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 ago
Cloud 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 ago
  Yeah running it on premise should be faster.
perlgeek 8y ago
The more fields you configure, the slower it gets. (That seems to be my impression, at least).
mxschumacher 8y ago
same for me. ~7s load times on a 100 Mbs connection with a new macbook pro are a daily encounter.
slider_thor 8y ago
Jira 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 ago
  1.5–2.5 seconds is slow. (Faster than I’m getting, though, I’ll give you that.)

tachang 8y ago

What are you doing that I am not? Jira is slow as hell and updating statuses take forever. Are you on an onprem version?

achamayou 8y ago
I’ve used two separate onprem versions, and they were slower than hosted if anything.
Cyclone_ 8y ago
Yeah it's onprem

sergiotapia 8y ago

I also liked my time working with JIRA tools, however these days I've moved on to Clickup. https://clickup.com/ https://clickup.com/ It's like they spent much more time refining the UX and feel of moving around clicking on things. It's pretty great.

lugg 8y ago
> It's like they spent much more time refining the UX and feel of moving around clicking on things. I just gave it a whirl - for an hour or so - so take this with a grain of salt. Looks much nicer, and there definately has been more effort put into the design compared to trello / jira. Thats about where things end for me though. I don't think the UX is refined at all, it's full of usability faux pas and their CSS could undergo some basic usability testing as well. Jira's usability isn't that bad if you use sane defaults and avoid overconfiguration. Jiras main problem (and its a big fucking problem) is responsiveness. I did have a look at their suggestion forum and it looks very active I think I'll give them another look in a few months to see if they've managed to reign in some of the BS or if it only gets worse. (I suspect the latter will occur for various reasons.) And please, don't take this harsh critique the wrong way, if I was choosing a platform today I'd probably pick them, beauty is a hell of a drug - just don't confuse a nice looking design with UX.