-
Bug
-
Resolution: Timed out
-
Low
-
10
-
Severity 3 - Minor
-
Issue Summary
When Next-gen issue is dragged from Backlog to Sprint section (Classic board), it will stay in Backlog section after page refresh (it only affects for Kanban next-gen project type).
Steps to Reproduce
- Have 2 projects; Classic Scrum type and Kanban next-gen project type.
- Create some issues in both projects
- Create a filter that include both projects
- Create a new board based on the above filter
- Go to the above board (Classic project) > Create a Sprint
- Move some issues from both projects to the Sprint
- Start the Sprint > Refresh the page
Actual Results
Issues from Kanban next-gen project type are not grouped in Sprint section (they stay in Backlog)
Expected Results
Issues from Kanban next-gen project type are grouped in Sprint section
Notes
- Those issues from Kanban next-gen project are still shown in Sprint Report
- Searching in Issue Navigator (Sprint = <Sprint ID>) doesn't return issues from next-gen project
- Issue history recorded that the issues from Kanban next-gen project are correctly added in the Sprint
Workaround
- Go to Kanban next-gen project configuration
- https://<URL>.atlassian.net/projects/<project key>/settings/features
- Enable both Backlog and Sprint
- Disable them again
| Form Name | |||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
[JSWCLOUD-18535] Next-gen issue is not shown in Sprint section in Classic board
Related to this issue is when the next-gen issue has an EPIC.
We have a classic project with two boards (Scrum & Sprint).
When the next-gen issue has an EPIC the issue dissapears from the Scrum board and only appears in the Kanban board.
Is there any workaround for this other than to link the next-gen issue to the next-gen EPIC?
Hi all,
Thank you for raising this bug and bringing it to our attention.
Within our company roadmap and work capacity, we try to address or review each bug request but admit that not each one will be resolved.
To continue the culture of being honest and open, we are closing this bug to focus on our upcoming roadmap for all Jira users.