Details
-
Bug
-
Resolution: Duplicate
-
Low
-
None
-
6.3.11, 6.4-OD-16
-
6.03
-
Description
NOTE: This bug report is for JIRA Server. Using JIRA Cloud? See the corresponding bug report.
When creating a JIRA instance from scratch, the following priorities are created by default:
ID | Name |
---|---|
1 | Highest |
2 | High |
3 | Medium |
4 | Low |
5 | Lowest |
If we create one issue with each priority and search for issues, they are correctly retrieved.
However, if we rename the priorities for numbers, and those numbers are the IDs of other priorities, JIRA will search for the IDs and not the priority names, bringing inconsistent results.
For instance, If we search for priority name "High", it will bring issues with priority set to "High".
Let's say we edit the priority names to the following:
ID | Name |
---|---|
1 | Highest |
2 | 3 |
3 | 2 |
4 | Low |
5 | Lowest |
If we search for priority name "2" (which was the High priority in the first example), it will bring issues with priority "ID" 2, not consistent with the expected results, since in the screen we select the priorities according to their names:
Attachments
Issue Links
- duplicates
-
JRASERVER-37238 If the Priority Name is only a Number, Issue Navigator will return issues matching its Name or ID
- Closed
- relates to
-
JRACLOUD-42492 Searching issues using the priority doesn't work properly
- Closed