3 ms·

I used to be in the "hate JIRA" camp but have basically done a total 180 on it. I'm convinced that most people that hate it have a poorly configured setup and d

by mikey_p 10y ago

I used to be in the "hate JIRA" camp but have basically done a total 180 on it. I'm convinced that most people that hate it have a poorly configured setup and don't know the difference between the frustrating workflow forced on them by their management, and what the software actually does. I've never seen a bug tracker with better keyboard commands, more powerful features, more ways of organizing stuff, more powerful querying, but all of that is just under the surface, and waiting for you to discover it. The default out of the box experience is simple, clean, works, and encourages best practices for software development.

seanjregan 10y ago
The more capabilities people have the opportunities they have to be great or be confused. It is a tough balance but generally speaking the flexibility of JIRA lets teams do some amazing things. We need to always we making sure it is harder for people to make mistakes but also need to make sure that our core users can have the flexibility they demand.
Karunamon 10y ago
As one of a small handful of JIRA/other atlassian app admins at my company, yeah, this. The problem with pretty much anything Atlassian makes is that it's too easy to setup, in that you can have a working, but non-performant, awful to use system without much hassle. Best advice I can give here is talk to your users. Find out what they think sucks about your setup, and then actually work on those things. Do you really need 20 custom fields filled in by hand, or could that be automated? Do your PMs have any idea how the query syntax works? (Send them to class for this - seriously!) Does your workflow really need 19 disparate steps each with their own triggers and conditions? Beyond a certain point, you can't even reason about the system anymore. Someone, somewhere is going to have to compromise.

by mikey_p 10y ago

seanjregan 10y ago

The more capabilities people have the opportunities they have to be great or be confused. It is a tough balance but generally speaking the flexibility of JIRA lets teams do some amazing things. We need to always we making sure it is harder for people to make mistakes but also need to make sure that our core users can have the flexibility they demand.

Karunamon 10y ago

As one of a small handful of JIRA/other atlassian app admins at my company, yeah, this. The problem with pretty much anything Atlassian makes is that it's too easy to setup, in that you can have a working, but non-performant, awful to use system without much hassle. Best advice I can give here is talk to your users. Find out what they think sucks about your setup, and then actually work on those things. Do you really need 20 custom fields filled in by hand, or could that be automated? Do your PMs have any idea how the query syntax works? (Send them to class for this - seriously!) Does your workflow really need 19 disparate steps each with their own triggers and conditions? Beyond a certain point, you can't even reason about the system anymore. Someone, somewhere is going to have to compromise.