[wpietri]

Personally, I hate it because it is too functional.

It has eight zillion features, all of them overlapping. It has so many fields, dimensions, views, and reports that I despair of ever getting a setup that usefully matches an actual workflow. The point of a work tracking system is to bring everybody together, but I regularly see people dealing with Jira by having their own separate tracking methods: docs, emails, spreadsheets, sticky notes on the wall.

I like Trello better because it's more straightforward. Less complexity means less chaos and an easier time getting a workflow representation that matches actual workflow.

But personally, I like things that are more straightforward still. E.g., my last company ran almost entirely on index cards, and we were very happy with that:

http://williampietri.com/writing/2015/the-big-board/

[jimbokun]

This is probably why I like JIRA better than you do, other people at my company configured everything, I just have to use it.

[komali2]

Yes, the same here, I came into a company with JIRA set up like a trello board, and all this awesome integration (stuff gets moved from "in progress" to "code review" automatically on a PR on that feature branch) and I got to work on top of the shoulders of giants.

[wpietri]

I think this works only if your process is standardized across your company. Which I think is generally a terrible mistake in software, because a) team needs can differ, and b) you can't improve process unless the whole company changes at once.