I was facing similar issue with many user reported, when I completed a Sprint it move all Done items to next Sprint. It was so confusing.
And I was surprised that the original "Done" status is not recognized as "Completed", then it auto move to next sprint... what's the problem of new update in Jira??
how can I exclude these items from current Sprint, or move it back to previous Sprint?
Hello @Bravo IT ,
❗ Root Cause: Jira only considers issues “Completed” if their status maps to the "Done" category — not just named “Done”
Just because your issue’s status is called Done, Closed, or Approved doesn't mean Jira treats it as "completed" in Agile terms.
Jira looks at the status category (not the name of the status).
Check if your Done status is truly “Done”
Go to Project Settings → Workflows
Click Edit workflow
Hover over your Done status
Check the status category color:
✅ Green = Done category (correct)
🔵 Blue = In Progress category (wrong!)
⚪ Gray = To Do category (also wrong)
If your “Done” status is not green, Jira won’t consider it as “completed” when closing the Sprint — so it moves to the next one.
To fix:
Go to Jira Settings → Issues → Statuses
Edit your status (e.g. Done, Closed)
Set Status Category = Done (Green)
This will ensure that Jira excludes those issues from future Sprints when closed.
🟢 Workaround 1: Create a Dummy Sprint
Create a "Recovered Sprint"
Move the incorrectly forwarded issues into it
Close that Sprint with just those items — this gives them proper sprint history
🟡 or Workaround 2: Edit Sprint via REST API (Advanced)
Use the Jira REST API to change the Sprint field of those issues back to the correct Sprint ID. This is helpful if you’re restoring history for reports.
Use Sprint Completion dialog → Check the "Incomplete issues" section
Use Automation to warn you if any "Done"-named status is not in the Done category
Hello @Bravo IT
Welcome to the Atlassian community.
When using a scrum board only the items in statuses in the column farthest to the right are considered "complete" at the end of the sprint. It doesn't matter what their status is, only that it is in the right-most column.
This also determines what will appear in the Backlog list in your Backlog screen.
Additionally if you have an issue that has subtasks that are in statuses not in the right most column, then the parent issue will be considered incomplete even if it is in the right most column.
When an incomplete issue is moved to the next sprint it retains its connection to the previous sprints that it was in. You don't need to "move it back" to the previous sprint. However, if you view the Sprint report for that sprint, you will see that the issues were considered incomplete.
If you remove the issues from the current sprint, and they are in statuses not mapped to the right-most column, then they will display in the Backlog list in your Backlog screen, because Jira will consider them incomplete.
So, the first question that needs to be answer is are the issues in statuses that are mapped to the right most column of your Scrum board? Can you share with us the board configuration screen that shows the mapping of statuses to columns for your board?
The second question is do you have more than one Scrum board with different mappings of statuses to columns that include these issues?
The third question is are these issues that have "incomplete" subtasks?
And the last question is what Type of project does this concern? Get project Type information from the View All Projects page under the Projects menu.
If what I have described does not match your situation (i.e. the issues actually are in the right most column), then you are experiencing a different problem and we need to ask different questions.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.