Details
-
Bug
-
Resolution: Won't Fix
-
Low
-
None
-
6.1.7
-
6.01
-
Description
NOTE: This bug report is for JIRA Server. Using JIRA Cloud? See the corresponding bug report.
Steps to replicate:
- Modify the default priorities to match the below:
id | sequence | pname ----+----------+--------- 1 | 1 | Blocker 2 | 2 | 1 3 | 3 | 2 4 | 4 | 3 5 | 5 | 4
- Use the Issue Navigator to search for:
priority = "3"
Actual Behavior:
JIRA will return any issues with priority = 2 or 3 as the ID of priority '2' is 3.
Expected Behavior:
JIRA would see that "3" (with quotes) is a priority name and would only return results by the name. Alternatively, would show a message explaining why it is returning both.
Workaround:
- Use the following to search:
priority = "3" AND priority != "2"
- Or rename the priorities (e.g.: "Level 3").
Dangerous Workaround:
This workaround is dangerous because it involves direct DB modification, and the order of operations is important if you are switching positions of any two items. You MUST test this on a staging environment first, and take a full backup prior to doing this in production. This is an example:
update priority set id = '4' where sequence = '4'; update priority set id = '3' where sequence = '3'; update priority set id = '5' where sequence = '5'; update jiraissue set priority = '3' where priority = '4'; update jiraissue set priority = '4' where priority = '8'; update jiraissue set priority = '5' where priority = '10000'; update changeitem set newstring = '3', newvalue = '3' where field = 'priority' and newvalue = '4'; update changeitem set newstring = '4', newvalue = '4' where field = 'priority' and newvalue = '8'; update changeitem set newstring = '5', newvalue = '5' where field = 'priority' and newvalue = '10000'; update changeitem set oldstring = '3', oldvalue = '3' where field = 'priority' and oldvalue = '4' update changeitem set oldstring = '4', oldvalue = '4' where field = 'priority' and oldvalue = '8'; update changeitem set oldstring = '5', oldvalue = '5' where field = 'priority' and oldvalue = '10000';
You must restart JIRA and re-index after performing these updates.
Attachments
Issue Links
- incorporates
-
JRASERVER-60762 Issue Navigator Is Showing Incorrect Results When Priority Name Is Set As Any Number Between 0 - 5
- Closed
- is duplicated by
-
JRASERVER-42492 Searching issues using the priority doesn't work properly
- Closed
-
JRASERVER-60762 Issue Navigator Is Showing Incorrect Results When Priority Name Is Set As Any Number Between 0 - 5
- Closed
- relates to
-
JRACLOUD-37238 If the Priority Name is only a Number, Issue Navigator will return issues matching its Name or ID
- Closed
- mentioned in
-
Page Loading...