We have a project and a custom issue type, we use a numerically based priority custom field across this issue type and in this issue type screens we never used a jira default priority field and for some reason, i see this priority field as minor in details view on a single ticket, just one out of 460 tickets which are based on the custom issue type. Why is this happening?
This happens on ticket view screen. We have default screen for all issue operations. Am i missing anything here?
Not really missing anything.
Jira will display the priority (and some other system fields) if they have data, whether they are on your view screens or not. In this case, even though you don't use the system Priority, this issue has somehow had one applied, so Jira shows it.
The usual culprits are (unusually) an admin making a mistake in setup and temporarily enabling the system field long enough for a user to populate it, and (the most common) an issue moving from a project where system Priority is used to one where it is not
I'd suspect the latter. Check the issue history tab to see if it was moved. Sometimes the default Priority will get set on issues and appear unexpectedly.
To hide the standard Priority field you can use a field configuration, but it may mess up the default reports for the project in older versions of Jira.
In the past, Portfolio for Jira required a high degree of detail–foresight that was unrealistic for many businesses to have–in order to produce a reliable long-term roadmap. We're tur...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs