-
Bug
-
Resolution: Fixed
-
Low
-
None
-
8
-
Severity 3 - Minor
-
1
-
Issue Summary
The next-gen "Group by" feature is not displaying the swimlanes in the issues' order.
If you compare the order of the issues in the backlog view and in the Active sprint view when the "Group by" option is defined by Sub-task, Epic or Assignee, the order of the swimlanes don't follow the pattern of the backlog view (Rank)
Environment
Jira Software cloud
Steps to Reproduce
- Create a new Scrum next-gen project
- Add stories to it and sub-tasks to some of the stories, or add Epics to the roadmap and Stories under it
- Access the Board view (active sprint view) and in the Group by options menu select Subtask or Epics
- Compare the order of the issues in the active sprint view with the backlog view
Expected Results
The order of the issues should be the same in both views
Actual Results
The order of the issues is different:
Notes
Workaround
Create a Classic board and edit its filter to return the next-gen issues.
- is duplicated by
-
JSWCLOUD-18550 Swimlane order when grouping by Subtasks should match issue rank order
- Closed
- is related to
-
JSWCLOUD-18060 When using the group by subtasks in a next-gen board, stories with subtasks no longer show their column status nor ID #
- Closed