-
Bug
-
Resolution: Unresolved
-
Low
-
None
-
8
-
Severity 3 - Minor
-
2
-
Issue Summary
When filtering issues that have been through multiple sprints, the order of the Sprints is displayed in random order and does not match the order in the Sprints field.
Steps to Reproduce
- Filter issues(through Advanced issue search) that have been through multiple sprints.
- Switch to List view.
- In the columns displayed, make sure to check the Sprint field.
- Verify the order of the sprints displayed for a particular issue and you can see that it does not match the order seen in the sprint field on the issue view page.
Expected Results
Since the Global issue navigator displays information from the Field, it should show the same order seen in the Sprint field when viewing an issue.
Actual Results
Sprints are displayed in random order and do not follow the order seen in the Sprint field when viewing the issue.
Workaround
Currently there is no known workaround for this behavior. A workaround will be added here when available
- is related to
-
JRACLOUD-90712 Sort inconsistency in the sprint field
-
- Closed
-
-
JRACLOUD-95346 Sprints Returned in Non-Chronological (Random) Order
-
- Gathering Impact
-
- relates to
-
JRACLOUD-61894 Order /sort sprints by name/ID using JQL when searching issues
- Gathering Interest