-
Bug
-
Resolution: Fixed
-
High
-
18
-
Minor
-
5
-
Issue Summary
When expanding the sprint picker dropdown when viewing an issue, the list of sprints returned are sorted in an inconsistent manner yielding different results at random times.
Steps to Reproduce
- Browse to an issue which has the Sprint field included in the issue view/edit
- Click on the Sprint field to expand its picker dropdown
- Enable the option Only show sprints in this project
Additionally, when we have more than 10 future sprints on the board, then the active sprint can not be seen when the check box (Only show sprints in this project ()) is on for the sprint field
Expected Results
The returned sprints are ordered in a consistent manner.
Actual Results
The sprints are displayed in an unordered manner, not alphabetical nor by their ID and they are ordered differently at random times.
Active sprints may not be included in the list returned.
Workaround
Currently, there is no known workaround for this behavior. A workaround will be added here when available
(To be able to select the correct sprint in the dropdown, type in the sprint name. This will narrow down the suggested sprints and hopefully show the right one.)
- is duplicated by
-
JRACLOUD-92406 Unable to select desired sprint name when there are similar name
-
- Closed
-
- is related to
-
JRACLOUD-90810 Ordering/Configuration of which Sprints and # of Sprints displayed in the dropdown selection field upon Issue Creation
- Gathering Interest
- relates to
-
JRACLOUD-81425 Sprints information under Sprint field is displayed in random order when filtering issues through Advanced issue search.
-
- Gathering Impact
-
- mentioned in
-
Page Failed to load
-
Page Failed to load
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
Hi, I'm from the team responsible for the sprint picker. I've made a change to ensure that at least one active sprint is always displayed when picking a sprint, hopefully this unblocks the majority of customers having this issue. There is more work to be done in terms of sprint ordering, but looking through the individual support cases it looks like missing active sprints is the more prominent issue that needs to be solved here.
The change has been fully deployed to production under a feature flag, which I'll now start rolling out over the course of the next few days, however we are able to target individual customers directly to unblock where needed.