-
Bug
-
Resolution: Unresolved
-
Low
-
None
-
7.6.2, 7.6.4, 7.12.3, 8.0.1
-
7.06
-
19
-
Severity 3 - Minor
-
5
-
Summary
After adding priorities in Jira (and ordering them), the Default Priority Scheme does not show them in the right order.
The Priorities screen in Jira administration states:
The table below shows the priorities used in this version of Jira, in order from highest to lowest.
and the Default Priority Scheme shows all priorities in Jira. The list shown in the Priority Schemes screen (for that Default Priority Scheme) and the list of priorities in projects using the Default Priority Scheme is ordered by ID of the priority, rather than the order shown in the Priorities screen.
When using the Default Priority Scheme, Jira will pick the middle-ish (based on the number of priorities) and use that as the default.
Steps to reproduce
- Add a few extra priorities to Jira
- Change the order in a way that the newest is in the middle
Expected results
The Default Priority Scheme and Priority Pickers display priorities in the same order as the Priorities Screen.
Actual Results
The Default Priority Scheme and Priority Pickers display priorities based on their ID, rather than the order of the Priorities Screen.
Workaround
Since this behaviour only affects the Default Priority Scheme, the best solution is to create a new Priority Scheme that has priorities in the correct order, and associate that scheme with each required project.
While it might be possible to adjust the default scheme in the database, in many cases it would be easier to simply create a new scheme, and use that (rather than attempting to adjust the default scheme.
- is related to
-
JRASERVER-68471 Unable to mark a priority as 'default' under Default Priority Scheme
- Gathering Impact
- relates to
-
JRASERVER-66660 Provide the ability to edit the default priority scheme
- Future Consideration