5 ms·

It's crazy how different opinions are on JIRA. I think it's the worst tool I'm forced to use - and have been - at all my dev jobs. It's slow, sluggish, the UX i

It's crazy how different opinions are on JIRA. I think it's the worst tool I'm forced to use - and have been - at all my dev jobs. It's slow, sluggish, the UX is horrible and it gets in my way. A lot of dev teams that are outside of product/project management claws simply opt for using whatever simple kanban board there might be(Trello, for example).

Narew 6y ago
I used to have same opinion when I used only JIRA. But on my new work we use all JIRA, Stash, Crucible, Bamboo etc ... and the way all of these tools work together is really powerfull
manicdee 6y ago
Every problem you mentioned with a Jira is some decision your IT folks made. The same every time I hear people telling me how awful the software is: they complain of autocratic workflows, forms being slow, forms being complex and having so many mandatory fields that they can’t get anything done. It’s all due to local configuration, some IT kiddo sees all these bells and whistles and levers to pull, so they turn them all on thinking more features is better. In the meantime the most efficient workflow I have has six states (planning, execution, UAT, deployment, warranty, closed) and it works just fine and stays out of my way.
- natch 6y ago
  Suspected as much. Not just IT people — it’s quite a playground for process wonks, and I mean that as a bad thing. I do love JIRA but wish it would stay simple in practice where I work. Unfortunately not the case at my current job.
- coblers 6y ago
  JIRA being slow and sluggish doesn't really have anything to do with configuration. It's a horrible tool to navigate UX-wise.
  - richardwhiuk 6y ago
    It's often deployed on completely underpowered servers.
    - deleted 6y ago
      [deleted]
  - kls 6y ago
    Some of that does have to do with how you configure it. JIRA is a swiss army knife and what you build out of it as a process and ticket management system can look very different from what I build out of it, and they can perform differently depending on how much automation, checks, and guards you put in it. I think the problem with JIRA is they don't really have a sane default install, it really feels like a bag of parts and then you assemble it. Maybe 2 or 3 opinionated templates that take a process end to end would help people, that just want to get started and that stare into the configurable abyss of JIRA and go "nope just want a ticket system".
  - manicdee 6y ago
    What are your recommendations for better UX?
- kossmoboleat 6y ago
  Atlassian's own hosted version was often very sluggish for me too, although granted that the self-hosted version were a bit worse...
jasonv 6y ago
Jira for a team of 20-30 developers, where I'm the CTO and we implement it together... I like it :-)

Narew 6y ago

I used to have same opinion when I used only JIRA. But on my new work we use all JIRA, Stash, Crucible, Bamboo etc ... and the way all of these tools work together is really powerfull

manicdee 6y ago

Every problem you mentioned with a Jira is some decision your IT folks made. The same every time I hear people telling me how awful the software is: they complain of autocratic workflows, forms being slow, forms being complex and having so many mandatory fields that they can’t get anything done. It’s all due to local configuration, some IT kiddo sees all these bells and whistles and levers to pull, so they turn them all on thinking more features is better. In the meantime the most efficient workflow I have has six states (planning, execution, UAT, deployment, warranty, closed) and it works just fine and stays out of my way.

natch 6y ago
Suspected as much. Not just IT people — it’s quite a playground for process wonks, and I mean that as a bad thing. I do love JIRA but wish it would stay simple in practice where I work. Unfortunately not the case at my current job.
coblers 6y ago
JIRA being slow and sluggish doesn't really have anything to do with configuration. It's a horrible tool to navigate UX-wise.
- richardwhiuk 6y ago
  It's often deployed on completely underpowered servers.
  - deleted 6y ago
    [deleted]
- kls 6y ago
  Some of that does have to do with how you configure it. JIRA is a swiss army knife and what you build out of it as a process and ticket management system can look very different from what I build out of it, and they can perform differently depending on how much automation, checks, and guards you put in it. I think the problem with JIRA is they don't really have a sane default install, it really feels like a bag of parts and then you assemble it. Maybe 2 or 3 opinionated templates that take a process end to end would help people, that just want to get started and that stare into the configurable abyss of JIRA and go "nope just want a ticket system".
- manicdee 6y ago
  What are your recommendations for better UX?
kossmoboleat 6y ago
Atlassian's own hosted version was often very sluggish for me too, although granted that the self-hosted version were a bit worse...

jasonv 6y ago

Jira for a team of 20-30 developers, where I'm the CTO and we implement it together... I like it :-)