Issues are appearing again after the sprint is closed - TEAM MANAGED PROJECT
Asked by Ganesh R:

Hello All,

I am working in a TEAM MANAGED PROJECT, I have completed 2 sprints and now I see the issues are appearing in the backlog from Sprint 1. Please explain why this is happening?


Answers:
author: Nikola Perisic
body: Hello [@Ganesh R](/t5/user/viewprofilepage/user-id/5558790) the issues that are not in the Done status will move to another sprint until they have been resolved.


author: Marc - Devoteam
body: Hi [@Ganesh R](/t5/user/viewprofilepage/user-id/5558790)

Is the last status "Done" of your workflow in the last column of the sprint board?

If this is not the case the sprint doesn't consider the issue as burned and it will reappear as not Done

comments: author: Ganesh R
body: Hi [@Marc - Devoteam](/t5/user/viewprofilepage/user-id/3796976)   

The columns look like this.  

![Screenshot 2024-09-05 170000.png](https://community.atlassian.com/t5/image/serverpage/image-id/345731i321956EA10200BF9/image-size/large?v=v2&px=999 "Screenshot 2024-09-05 170000.png")

Why am I not getting issues from other closed sprints? How do I change the workflow to be verified instead of Done? Or Should that be Done strictly?


author: Ganesh R
body: This is how workflow looks like [@Marc - Devoteam](/t5/user/viewprofilepage/user-id/3796976)

![Screenshot 2024-09-05 170523.png](https://community.atlassian.com/t5/image/serverpage/image-id/345736iB85CA2C156E97BA6/image-size/large?v=v2&px=999 "Screenshot 2024-09-05 170523.png")


author: Ganesh R
body: [@Nikola Perisic](/t5/user/viewprofilepage/user-id/5494176) please check the snapshots attached. Should I name the last card as DONE only?


author: Marc - Devoteam
body: What is the status of the issue from Sprint 1, is this verified or other?

Your board seems fine and the WF also, there is no need to have the name Done.

Done statuses in Jira are represented by the color green


author: Ganesh R
body: Yes it is Verified only


author: Ganesh R
body: [@Marc - Devoteam](/t5/user/viewprofilepage/user-id/3796976) plz check

![Screenshot 2024-09-05 172124.png](https://community.atlassian.com/t5/image/serverpage/image-id/345740iC66A6C39EC6BABD7/image-size/large?v=v2&px=999 "Screenshot 2024-09-05 172124.png")![Screenshot 2024-09-05 172055.png](https://community.atlassian.com/t5/image/serverpage/image-id/345741i9B062085EE3A40D8/image-size/large?v=v2&px=999 "Screenshot 2024-09-05 172055.png")


author: Marc - Devoteam
body: Was the order of the board changed before after or during Sprint 1?


author: Ganesh R
body: I am not sure, but how does that affect?


author: Marc - Devoteam
body: I at first had the columns of your board differently ordered, it could be that Verified wasn't the last state and the issues where not recognized as burned in the sprint

To fix it no, the simplest what is to re-open the verified issues and add them to the current sprint and place them in verified again.


author: Ganesh R
body: [@Marc - Devoteam](/t5/user/viewprofilepage/user-id/3796976) How to reopen and add issues to sprint?


author: Marc - Devoteam
body: Hi [@Ganesh R](/t5/user/viewprofilepage/user-id/5558790)

Move your issue to another status in your workflow.

Your workflow states you can transfer any issue from and to any status.


Tags: backlog

cloud

jira-cloud

new-to-atlassian

new-to-jira

new-to-jsm

sprint-report

team-managed-projects