Done tickets from last sprint remove from the current sprint
Asked by maja_vuchkova:

Hi, I have tickets from the last sprint with the status "Done" that were not automatically removed when I closed the sprint. Now, I can't see the sprint in the timeline, and all the "Done" tickets have moved to the next sprint. Is there a way for me to go back, reopen the sprint, automatically remove these tickets when I complete the sprint, and move on? I might have done something wrong. Can someone help?


Answers:
author: Trudy Claspill
body: Hello [@maja_vuchkova](/t5/user/viewprofilepage/user-id/5551352)

Welcome to the Atlassian community.

Are you working with a Team Managed project or a Company Managed project? You can get that information from the Type column on the View All Projects page under the Projects menu.

When you Complete a sprint you should be getting a pop-up that tells you how many issues are Complete and how many are Incomplete.

![Screenshot 2024-07-24 at 4.16.40?PM.png](https://community.atlassian.com/t5/image/serverpage/image-id/337760i752DA5360BBBD299/image-size/large?v=v2&px=999 "Screenshot 2024-07-24 at 4.16.40?PM.png")

Did you get an pop-up like that indicating you had a number of open issues?

When you Complete a sprint, only the issues in the column farthest to the right will be considered "complete". Issues in any other column, regardless of the Status value, will be considered "open" and will be moved to the next sprint or backlog as per your direction.

In your Scrum board is the "Done" status mapped to the column farthest to the right on the board? If the Done status is not mapped to the column farthest to the right on the board, then those issue would be considered "open" at the end of the sprint. Can you show us the mapping of statuses to columns for your board?

If that doesn't align with what you have experienced there are some other things we can recommend investigating to find the cause.

comments: author: maja_vuchkova
body: It's a Team Managed project. I saw the pop-up, but I had already updated the status to the latest one yesterday. As a result, all the "done" tasks moved to the next sprint. Is there a way to reopen that sprint, or do I need to close this one and change things in the next one before moving forward?![Screenshot 2024-07-26 135652.png](https://community.atlassian.com/t5/image/serverpage/image-id/338163iCD955B3AF72F4BEB/image-size/large?v=v2&px=999 "Screenshot 2024-07-26 135652.png")


author: Trudy Claspill
body: If your system is configured to allow Parallel Sprints then you could reopen the previous sprint. To do that you would need to go to the Sprint Report to find that sprint and reopen it. But that alone will likely not solve your problem.

An issue can't be in more than one active sprint at a time, and I'm not sure what Jira would do if you tried to reopen that sprint when it's issues are already in an active sprint.

At this point it may be better to continue with the current sprint and see what happens when you start the Completion process. If you have the flexibility to pause the completion of the current sprint, then I recommend you do so, so that the state of the system at that moment can be reviewed.

I would suggest that you look at the sprint report for the previous sprint and see in which group your previously done issues are listed. They should've been listed in the Issues Completed in Sprint section. If they were not, that problem needs to be investigated, but you may have to wait until you are ready to end your current sprint to see if the problem occurs again. If it does, then before starting another sprint the problem should be investigated more.

It would also be a good idea to let your Jira Admins know about this issue. If it becomes necessary they can open a support case directly with Atlassian. Then, with you admins' permission, Atlassian engineers could connect directly to you system to look at the data.

Here we are a community of users. We can offer you debugging tips, but we can't access your system directly. So there is a delay while we ask you questions, wait for your response, then offer new suggestions.


Tags: cloud

jira-cloud