Of course, while I'll agree about Jira being unfortunate, I'll say from experience it's the "committee" of people that end up making up tons of fields imagining that they have some utility. Jira is complicit by saying "sure thing, as many required and cross-linked fields as you like!"

We have "Priority", "Severity", "Importance" on top of the sort order having some other indication of relative importance, all must be filled. Opening an item in one place requires you to have an item already opened in another place and that one requires a project id from some other tool to know who to charge, in theory. In practice it's not hooked into any charging system, but they imagine one day departments can charge each other for fixing items. We also have about 4 additional "describe the ticket" fields and in addition to the title, there's a 'One line summary'. All required.