Jira tasks which are Done and Resolved are having the sprint value populated at sprint closure

[Brian Richardson]

We have one Jira project with a very strange thing happening around the sprint values being populated on work which is moved to Done and Resolved in a particular sprint.

The jiras are being added to the next sprint even though they are Done and Resolved. We now have jira which it has happened 5 sprints in a row.

The team that close the sprint confirmed they are not doing anything which would bring these done items into the next sprint but we are unsure what's different in this jira project and the sprint process compared to all of the other projects and sprints we have working correctly.

If anyone has any suggestions it would be great. 

Thanks 

[Bill Sheboy · Accepted solution]

Hi @Brian Richardson -- Welcome to the Atlassian Community!

Jira Scrum boards consider a work item as "completed for the Sprint" when it is in a status value that is mapped the far right board column.  Otherwise, they are not considered completed and move to the backlog or next sprint, depending upon what was chosen.

Did you check the board configuration for the status mapping?

If that is not the case, please check if an automation rule is updating the issues even though they are considered completed for the sprint.  To do that, check the automation audit log for any rules triggered on Sprint Completed or Work Item Transitioned to your "done" status.

Kind regards,
Bill

[Marc - Devoteam · Accepted solution]

Hi @Brian Richardson 

How is the sprint board configured?

Is the "done" state of the workflow mapped to the last board column?

Issues in a sprint are only considered burned if the last column in the board is based on a status from the "Done" category, so a green status.

[Brian Richardson]

Oh that's well spotted, without seeing it!

They had moved the Cancelled column over to the right, passing out the Done column. That is different to the other boards we work in. I'll have them update it now and see how that works for the next Sprint closure. 

Thanks so much for responding to the question, very much appreciated.