-
Suggestion
-
Resolution: Won't Do
-
1
-
10
-
Hi everyone,
Thank you for raising and voting on this suggestion. Your feedback is invaluable in shaping and enhancing Jira for all users. Given the high volume of feature suggestions for Jira, we must prioritize those that provide the most value to the majority of our users. After a thorough review by the team, we have decided that we will not be able to implement this suggestion in the immediate future.
Please remember that jira.atlassian.com is only one of many inputs for our roadmap. We’re continuously learning, analysing and interviewing customers to make Jira better. We encourage you to also share your feedback through Atlassian Community. Please also check out latest updates and upcoming plans from the Jira Cloud roadmap and the Atlassian Cloud release notes blog.
We understand that our decision may be disappointing. Please don't hesitate to contact me if you have any questions or feedback.
Regards,
Eoin
Product Manager, Jira Cloud
Problem Statement : Completing a cross-project Sprint creates confusion when Incomplete Issues exists.
Description: When a sprint is used among different projects, if we try to complete it and there are issues which are incomplete, no matter what option we choose, all issues belonging to different projects will move to backlog. However issues belonging to project from where we are completing sprint goes to the chosen option - next sprint, selected sprint or backlog.
This adds an extra step where issues from remaining projects needs to be assigned to required sprint again.
Details:
Below an example has been used:
Projects = Project A and Project B Issues = Issue 1 (in project A) and Issue 2 (in project B) Active sprint in project A = Sprint-A 1 Next sprint in project A = Sprint-A 2 Next Sprint in project B = Sprint-B 3
Example 1
Issue 1 and 2 are part of Sprint-A 1. When we complete sprint from board of project A, we will options to :
a) Move issues to next print : This will move Issue 1 to Sprint-A 3 and Issue 2 to backlog
b) Move issues to "Sprint-A 2" : This will move Issue 1 to Sprint-A-2 and Issue 2 to backlog
c) Move issues to backlog: will move all cases to backlogs of respective projects.
Example 2
Issue 1 and 2 are part of Sprint-A 1. When we complete sprint from board of project B, we will options to :
a) Move issues to next print : This will move Issue 1 to backlog and Issue 2 to Sprint-B 4
b) Move issues to "Sprint-B 3" : This will move Issue 1 to backlog and Issue 2 to Sprint-B 3
c) Move issues to backlog: will move all cases to backlogs of respective projects.
Current Behaviour : This behaviour seems to be by design. When we complete sprints, in option we will get sprints which belong to the same project from where we are completing it. And whatever option we choose, it will apply only to native issues and the issues belonging to other project will always move to backlog.
Requirement: All issues from all projects should move to the sprint or backlog as selected while completing Sprint.
Similar behaviour is observed when we have same project but different boards and same sprint is used among all boards.
When we use different boards with different board filters, in that case similar behaviour is observed.
Ex: Board A and Issue A (Task ) and Issue(Bug) while Board B has filter which only displays Bug so on board we see only Bug and no Task.
Here if we complete sprint from Board B, it will show 2 incomplete issues. And say we choose to move issues to next sprint, it will only move Issue B (which was visible on it) to next sprint. Issue A which was visible on board A will be moved back to backlog.
This behaviour is related to the board filter, not the project directly.
Only incomplete issues that are included in the main filter query of the board where the "Complete sprint" action is used will be moved to the selected sprint. (Subfilters on the board have no effect on this.)
Workaround
- Create a board with a filter set to include all projects that are included in these sprints.
- eg. For the example above, create an additional board in either project where the board filter is:
Project in (A,B) ORDER BY Rank ASC
- eg. For the example above, create an additional board in either project where the board filter is:
- Create and close your sprints on this new board, and all of the issues will be rolled over to the selected next sprint as expected.
The day-to-day work can still be done on more limited boards that suit your teams, as long as the sprint is closed on a board that can see all of the issues in the sprint.
- is related to
-
- Gathering Interest