I view Jira as the embodiment of the misguided software engineering practice of trying to generalize and abstract too high level of a task of something like "pr

I view Jira as the embodiment of the misguided software engineering practice of trying to generalize and abstract too high level of a task of something like "project management" and distill it down into one tool. While the Golden perfect abstraction handed down for the heavens by the gods is what you seek, it ultimately passes down complexity to end users through its generic approach. You need to create opinions within the generic world and then your team needs to understand Jira's abstraction combined with the opinion your company builds around it that's probably not documented. The end result is unless you're running a large project that really requires the functionality possible in Jira where creating the overhead or overloading something simpler isn't practical, then you're probably better off using something simpler and more opinionated--a nice simple solid framework to keep everyone on track.