Live data from Hacker News

Trello, “Jira Sucks”, and Tool Dysfunction

hackernoon.com

11–20 of 71 posts

Re: Trello, “Jira Sucks”, and Tool Dysfunction

#11
I miss using JIRA.

We used Trello, but boards were changed monthly. It was a nightmare. Then Asana which emails me endlessly and it takes so long to open. And now Zube which feels weird to put things in which aren't suited to dev tickets and getting anything right in the balance

Re: Trello, “Jira Sucks”, and Tool Dysfunction

#12
post #3

I have been using Jira at work for the last 10 months or so, and have been using trello for personal stuff for more than a year and a half. I dunno, but Jira doesn't looks so bad to me. To be quite honest, "Jira sucks" really looks like a meme to me, that people carry around for some reaons. I am not a jira enthusiast, nor i am endorsed/funded by atlassian in any way. Jira is a tool to me, and it does it job.

I think people associate JIRA with middle managers who "work" all day in JIRA and foist draconian JIRA "processes" on everyone. eg: My current manager wants us update all open JIRA tickets every morning with "current status" .

Not sure why manager types like JIRA though..

Re: Trello, “Jira Sucks”, and Tool Dysfunction

#15
My problems with Jira:

Permissions around issues and their state are so granular they beg to be abused.

Permissions aren't granular enough to allow teams to individualize their project's workflow as their needs evolve.

Jira constructs like states are reused in weird ways for other functionality. My favorite is the abuse of states to try and implement kanbahn style swimlanes; states which are global to an org and can thus get odd workflows attached to them by someone else.

Administered with a light touch, Jira can be fine. But it's never administered in such a fashion. NEVER.

Re: Trello, “Jira Sucks”, and Tool Dysfunction

#16
Been using both for years, at multiple orgs, and can say with confidence JIRA does suck. Everyone in my org had given up trying to use it, I went through the pain and don't wish it on anyone... then there's Trello, it just works expected.

With JIRA, prepare to invest significant pulling your hair out if you want to use any features. It's amazingly difficult to enable the use of the Trello-like board feature.

Go ahead, try enabling the "Agile" feature and see, it doesn't work out of the box!!! Have fun digging through Google to figure out why you're getting cryptic errors, only to finally figure it's because....

Oh, you have to set up additional permissions to enable it.

Oh, and also enable a certain field (epics) but this needs to happen in the back-end, as it's some SQL query to enable it.

Oh, but you want to sort issues by drag-drop like a real board? Nope. First go find the right permission to actually enable sorting!

Oh, but it still wont let you sort! Did you forget to 'sort by ASC' in your filter query? Otherwise, no drag-drop sorting for you!

Why those things aren't just enabled when you created the board in the first place, boggles my mind!

Re: Trello, “Jira Sucks”, and Tool Dysfunction

#17
Jira makes it easy to create a sucky tool, but the real reason is always that your organization has created a sucky process. I should know, I work for a large and instantly recognizable company and our process is waterfall in agile's clothing. Sadly we have to work in a world where we have two internal organizations, and one uses Jira and the other VersionOne and both are configured to enforce this watery scrum process.

Re: Trello, “Jira Sucks”, and Tool Dysfunction

#19
post #3

I have been using Jira at work for the last 10 months or so, and have been using trello for personal stuff for more than a year and a half. I dunno, but Jira doesn't looks so bad to me. To be quite honest, "Jira sucks" really looks like a meme to me, that people carry around for some reaons. I am not a jira enthusiast, nor i am endorsed/funded by atlassian in any way. Jira is a tool to me, and it does it job.

I think people associate JIRA with middle managers who "work" all day in JIRA and foist draconian JIRA "processes" on everyone. eg: My current manager wants us update all open JIRA tickets every morning with "current status" . Not sure why manager types like JIRA though..

I hate JIRA, but I noticed something. If I tell people to do something, they won't do it. If I create a ticket in JIRA it has a much higher probability of getting done. It's not been too bad, after I got over the hate of not having real markdown and the 100 fields when a ticket is created that are mostly unused.

I prefer little to no process, but the work has to be organized some how, and using git with emacs and org mode wouldn't be nice to most :)

Re: Trello, “Jira Sucks”, and Tool Dysfunction

#20
Tools drive the way we use them. If most people using Jira ends up with a process that sucks and most people using Trello don't, maybe it really is the tool that's making the difference.

(Jira sucks because it's anti-employee-empowerment by design; everything is oriented around mandatory fields, mandatory workflows, and requiring approvals. In theory a good manager should work around this, but defaults are important. I fear the same thing happening to Trello)

Post reply on HN