When trying to close out sprints we are having an issue where items that are done are being categorized as incomplete and Jira wants to move them to another sprint/backlog. We are only seeing this within one project and previously in this project did not have this issue when closing a sprint. I contacted atlassian support and they provided me with this link: https://confluence.atlassian.com/cloudkb/best-practices-on-using-the-resolution-field-968660796.html. Followed these instructions step-by-step which led to an even more bizarre behavior where now items that were "cancelled" are shown as done at sprint close by no other issue types are. I have compared the post functions and resolutions for all statuses and transitions and they appear the same. So I am not sure what I am missing?
In most sprints for an issue to be done it must have a value in the resolution field. Any value. If your 'cancelled' issues have a value in resolution they will show as done. Technically, if they are cancelled they are basically 'done' since no more work is needed. If on the other hand you didn't have a resolution in the cancelled issues and now you do they will show as done
In our case we have a resolution for both "done" and "cancelled" items. But when we go to close only the "canceled" are being identified as done and the "done" items Jira is trying to force us to move to a new sprint/backlog. So basically "cancelled" is working as we would expect but "done" is not.
That's weird. No matter what resolution you pick, issue should be resolved. Is your close status in green color?
Yes. Status is green and resolution field is filled in. This just popped up for us within the last week and just on one project. We even have projects sharing this workflow and on the other this issue isnt appearing.
https://community.atlassian.com/t5/Jira-questions/0-issues-were-Done-when-completing-Sprint/qaq-p/366330
This was the issue, way more simple then what I was assuming. We recently added a "Cancelled" column after "Done" and that was what caused the issue.
It looks like you're new here. Sign in or register to get started.
