Tickets with "Completed" status are moving to next sprint when closing current sprint.

[David]

We have a workflow for our development work. The last status is "Development Complete". It is setup as a "complete" status and shows in green. My expectation is Jira recognizes these issues as done and keeps them in the current sprint when it is closed.

However, when I complete a sprint, Jira sees these issues as not complete and keeps moving them to the next sprint. What am I doing wrong?

I want to make sure that when an issue goes to "Development Complete", Jira sees them as complete.

Thanks

[Tessa Tuteleers · Accepted solution]

Hi @David ,

Jira recognizes issues as done if they are in the right most column om the sprint board.
Do you maybe have another "green" (or any) status-column at the right of your "Development Complete" on the board?

All your "closed" statuses should be in the same rightmost column of your board.

Hope this helps! 

• Tessa

[David]

Tessa,

This could be the issue. We currently filter out all the "Done" statuses because it keep the board clean, but I'll update the board to include this status in the far right column and see if that helps.

Thanks

[Joe Pitt]

The resolution must also be set

[Tessa Tuteleers]

On cloud (weirdly), no. It doesn't even have to be statuscategory done. Even issues in "to do" are marked as completed (for the sprint),  as long as they are in the rightmost column :D

[Fabian Lim]

Hi @David

I would check the status category of the "development complete" status. Most likely is not set to "done".

Options: 

1. Change the category status of the status. However, if other projects/boards are using the status as an in progress status they will he affected.
2. Introduce another status such as closed to ensure that they are done after dev complete.

Cheers

[David]

Please see attached screenshot. The status is set to a category of "Done". I was hoping to use this status as it is more descriptive than just Done.

[Tessa Tuteleers]

@Fabian Lim , if the status is - as mentioned - green, it should be in the right category. On cloud, the location of the column is of importance as well (strangely enough), and not only the status or resolution.

[Fabian Lim]

Feel free to change it.  Just note that if if other projects are using the same status and don't want to identify them as "Done", their boards will be affected. Meaning, even if they want to identify them as "In Progress", their tickets will be closed after the sprint.  

Cheers.  

[Monika Marko]

So, does it matter whether the resolution is set or not, for this problem to stop recurring? 

We have 6 statuses that have a status category "done" Also, the boards are configured to use the most far right column to map all the 6 "done" statuses...

Resolution, however is not set in any except for the Jira default: Done✅ 

After reading a lot of these posts, I have started to gather that in Jira cloud, for this problem to not occur all three conditions below, must be met: 

1. Status category must be set to: Done (green)
2. Resolution for the all the Done statuses except the Jira default, must be set 
3. All the "Done' statuses, must be mapped to the far, most right column of that board, for the sprint to recognize a complete issue = done 

Could someone validate this assumption for me, please? (I am secretly hoping that I am wrong 🤞🏽😊