Why are done tasks from previous sprint still listed in current sprint?

[Tanishka Bansal]

I am in a company managed project. And fixed tasks from previous sprints are getting listed in current ones too.

[Trudy Claspill]

Hello @Tanishka Bansal 

Are the issues in statuses that are mapped to the column farthest to the right on your Scrum board?

[Tanishka Bansal]

yes

[Tanishka Bansal]

these issues dont only show on new sprints list, but the new sprint also gets listed in their sprints list field. 

[Trudy Claspill]

Can you show us the details of an issue that was in the column farthest to the right when you completed the sprint and is now showing up in another sprint? Can you also show us the details of the History tab for that issue?

And can you show us the Status/Columns mappings from Board Settings for that board?

And can you show us the Sprint Report for that same sprint, showing the bottom section of the report where it lists Completed and Incomplete issues?

Are the sprints to which these issues are getting assigned sprints created in the same board or another board that also displays these issues?

[Tanishka Bansal]

This is a very old issue that I fixed in 2022 but its still showing,  and it automatically gets added to newer sprints everytime

[Trudy Claspill]

What is the actual Status assigned to that issue?

Please show us the Columns page from Board Settings for your board.

[Tanishka Bansal]

See the issues listed in completed outside the sprint are the ones that are carried from previous sprints

 Its in the same board

[Trudy Claspill]

When you complete the sprint you should get a pop-up about how many issues were completed and how many were incomplete and will be moved to the backlog/next-sprint. Is the count in that pop-up reflecting all these issues that are in the Fixed column?

Are other issues that transitioned to Fixed within the scope of the sprint getting moved to the backlog/next-sprint, or only these old ones?

[Tanishka Bansal]

I dont remember the answer for the first question.
For the second, all issues are moved to next-sprint

[Trudy Claspill]

Do the issues that are moved have any subtasks? If so, are the subtasks set to Fixed also?

Beyond that I am stumped about what could cause this, and would recommend you ask a Jira Administrator to open a support case directly with Atlassian.

https://support.atlassian.com/contact/#/

[Trudy Claspill]

I know I have seen other posts in the user community where other people have described a similar problem. I'm trying to find one where the poster ended up getting a solution, but so far all the posts I have found have not matched your scenario.

In the interim I would recommend that you contact Atlassian support directly on this issue, and please report back to us what you learn.

[Alex Koxaras _Relational_]

Hi @Tanishka Bansal 

Do these "Done" items have a resolution set? Or they just appear in the done column of your sprint board?

[Tanishka Bansal]

They appear in done column of my board

[Alex Koxaras _Relational_]

If they don't have a resolution set (a check mark next to the status on the issue view), then Jira doesn't consider them resolved. And that's why when you move them to the next sprint, they are still there.

[Tanishka Bansal]

Ahha, but I see it marked as Done

[Trudy Claspill]

@Alex Koxaras _Relational_ 

I believe that is an inaccurate statement.

With a Company Managed project, issues in the column farthest to the right are considered "complete" when completing the sprint, even if that column does not contain a "done" status and the issues do not have a Resolution value.

The only defining factors for "completeness" of issues when completing a sprint are:

1. The issue is in a status that is mapped to the column farthest to the right on the board.

2. If the issue has any subtasks, those are also all  in a status that is mapped to the column farthest to the right on the board.

[Alex Koxaras _Relational_]

@Trudy Claspill you are right! I thought that it would be ok, if you had a "done" status and had set the resolution on that field via column mapping. To me this is strange..

[Alex Koxaras _Relational_]

@Trudy Claspill actually based on the documentation https://support.atlassian.com/jira-software-cloud/docs/complete-a-sprint/, an issue must be marked as done (e.g. have a resolution). It doesn't state anything about being on the furthest right column on the scrum board. :/

[Trudy Claspill]

I suspect that it says that because best practices indicate that a "done" status should be the last status on the board. Explaining that it is possible to have a board where you don't use "done" as the last status would be encouraging anti-patterns.

The documentation doesn't actually say that it has to have a Resolution value, and being in a green/done status does not actually guarantee that the issue does have a Resolution value.

[Tanishka Bansal]

What should I do? So that they are not reflected into new sprints

[Brian Bristol]

Did you ever find an answer to this question.  I am having the same problem.