[dragonwriter]

> If jira didn't have the ability to make it crap

Then your managers would buy a tool that did instead.

> maybe just try not to smush existing ms CRM workflows into a tool for devs.

If your employer wants a tool into which those workflows can be smushed and wants devs integrated into those flows, that’s what they’ll get.

Blaming a tool for supporting your management’s desires is...missing the people obviously responsible for the working conditions that are frustrating you.

[aunty_helen]

Jira existed as a better product before this and gained popularity without this functionality. I used and championed old jira in this business but hadn't used it for some time.

A better realisation would have been that one tool isn't going to integrate everything in your business from developing software to dealing with customers billing.

[dragonwriter]

> A better realisation would have been that one tool isn't going to integrate everything in your business from developing software to dealing with customers billing.

The trend (e.g., ERP and BMS) is definitely toward that in a much deeper way than broad use of JIRA alone represents. The “better realization” is probably more subtle, and involves more respect for the line workers in defining how their work is done and what the requirements are for the components of a broad enterprise-wide automation system that they interact with are, and balancing that with the information preferences at higher levels so that the latter are satisfied (and maybe compromised in some ways) in a way which preserves the ability of the line workers to deliver business value.

But, in either case, not having that realization is management issue, not a tool vendor issue.

[CRConrad]

Sure, but that still sounds like it was your management that should have had this realisation -- but didn't. That's a fault with your management, not the tool.