At the time completing sprint in JIRA for team-managed project done items are moving to another sprint. How can I avoid the done items moving to another sprint?
Have you seen this Help article?
Not sure if this applies to you, but the description resembles yours:
Diagnosis
Issues in the 'Done' status are not being detected as completed before closing a sprint. As a result, these issues will be moved to the backlog or the next sprint
Cause
The 'Done' column is not at the end of the board.
Solution
Check to make sure that the 'Done' column is at the end of the board.
@Aaron Morris Thanks for the solution as the done column was not moved to end of the board. Once I was able to configure board and moved done column to end of the board the done did not move to subsequent sprint.
Thanks for your supports.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello @Abdul Wahab
Welcome to the Atlassian community.
For future reference you may get better responses if you post Jira questions in the forum specifically for Jira.
https://community.atlassian.com/t5/Jira-questions/qa-p/jira-questions/
Can you provide screen images of what you see when you start the sprint completion process? You should get a pop up that tells you how many issues are completed and how many are open.
Can you provide a screen image of your board, pointing out in your board the issues that you consider "done" that are moving to the next sprint.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Here is an example of a Team Managed scrum board that has two statuses in two columns where the Resolution field is set for both statuses.
Only the one issue in the right-most column will be considered complete at the end of the sprint. Notice that the dialog says there is 1 complete issue and 2 open issues.
Even though the issue in the "Done" column (second from right) has its Resolution set, it is considered "incomplete" because it is not in the right-most column.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I now realize I initially overlooked that this is a Team-managed project, and the behavior makes more sense given the setup. In such projects, Jira treats issues as "Done" if they are in the far-right column, regardless of whether the resolution field is set. This differs from Company-managed projects, where both the column mapping and the resolution field determine the issue's completion status.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
@Trudy Claspill Thanks for the response, as I configured board and moved done column to the right most of the board. I was able to close the sprint and only move open items to new sprint.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Your statement is incorrect concerning Company Managed projects. Consider the following Company Managed project Scrum board. The right-most column is mapped to the In Progress status. The issue in it does not have the Resolution field set.
However if I complete the sprint the issue is counted as "complete".
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You're right. I apologize if I led anyone to the wrong solution.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Check if the post function on the last transition sets the resolution to issue. If there is no resolution, Jira does not consider the issue completed.
If it is not already set, you need to add a post function similar to the one shown in the picture.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You can create and use a Jira Automation rule to set the behavior of DONE issues.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.