[balex]

I was actually fairly pleased with Jira. Or rather the results of putting in the effort to build the flows we wanted.

Sure, building the forms and the workflow is an annoying experience. If Jira admin hasn't set up a good separation of templates, things get mixed up and cluttered (for project admin tasks). And it feels like you're working for the system instead of it working for you (again, when building your flows).

Still, once you get used to Jira's way of putting things together, building what you want becomes "not so bad". And you can have pretty much whatever process you want in place.

I think devs dislike it because it's riddled with layers upon layers of abstractions targeting enterprise deployments. Meaning if you want something quick and simple, it's probably the wrong tool.

But at the end of the day, it's about the process you build and making sure the tools serve it (mostly on the daily work level rather than admin). Jira let me refine the process and didn't get in the way of others on the team. Frankly, we liked it.

[SteadBytes]

> But at the end of the day, it's about the process you build and making sure the tools serve it

This seems to be the key. The _process_ is important and Jira (or another tool) _can_ be used to help implement that process, but Jira itself is not the process.