|
|
|
|
|
by Majestic121
1457 days ago
|
|
I don't know anybody that likes using JIRA, but to be fair I don't know anybody that likes to use Asana either. I might be wrong, but I think those tools are dedicated to something people don't like to do by default (planning, going through bureaucratic processes), so they don't like the tool either. But for some reason, they convince themselves that they don't like to go through Bureaucratic Processes because of JIRA/Asana/etc... and that if only the tool was better it would be a breeze, when in my experience the process is the real issue, rarely the tooling (even though it surely can be improved) |
|
A bit more seriously - it's not only about Bureaucratic Processes. UX matters. If you need to deal with "Bureaucratic Processes" using a terrible UI, it makes things worse.
Jira's UI is notoriously bad. Very slow. And the worst of all are the UX inconsistencies in Atlassian's products. Things behaving differently in Jira vs Confluence or even within Jira itself. For example, being able to use markdown when creating an issue but not when editing it (or vice versa, I don't remember).