I work at a large company that uses Jira. I had a need to create an issue tracking system for a non-IT org with a large volume of repeatable, largely repeatable

I work at a large company that uses Jira. I had a need to create an issue tracking system for a non-IT org with a large volume of repeatable, largely repeatable tasks with an easily defined workflow and the need to track various approvals and decision points. “Perfect! I’ll reuse a tool we already have! Save everyone money, document and standardize our processes! It’ll be great!” Nope. Our instance of Jira was set up for IT projects only and could not be set up for any other workflow. I tried to work around the administrative limits only to find a mess of tags and types and requirements that demonstrated that absolutely nobody had made any effort to adopt standard taxonomies even in the IT space. It’s not a perfect tool, and there’s enough wrong with it that both the “dysfunction taints Jira” and “jira is inefficient” crowds can be right. But it really is a good enough tool that does not do nearly enough to encourage its good enough use.