0 issues were Done when completing Sprint

[Chiel Schutter]

Hi,

I created a custom issue type that I use for a certain project. We don't use stories in our sprints but a standard issue with the estimation in hours. I created an Agile board, started the sprint and everything went well the last 2 weeks. Untill today when trieing to complete the sprint.

When completing the sprint I receive the message that 0 issues were done, but all the issues have the Status "DONE" and Resolution "DONE". I figured out that it has something to do with the status / resolution and maybe my custom workflow.

So I added several test issues to the active sprint to test if I was able to see that some issues were regonized as "done" when completing the sprint. I added the following test issues:

- Closed (fixed)

- Closed (unresolved)

- Closed (Done)

- Resolved (fixed)

- Resolved (unresolved)

- Resolved (done)

- Done (done)

- Done (fixed)

Ofcourse, i added the status to the corresponding column of the Agile board after adding these test issues.

But you can guess, still when completing the sprint I get the message that 0 issues were done and that all issues will be added to the backlog again.

What am I doing wrong here? I just want to complete the sprint, all issues are completed...

Cheers,

Chiel

[Maarten Cautreels · Accepted solution]

First thing that comes to mind: did you configure the Closed status to be the last column in the status columns?

[Sachin Dhamale]

Hi Maarten, 

does Done Columns is neccessory to recognize the completed ot done issue

[Maarten Cautreels]

Hi Sachin,

In any board the last column is considered the Done/Closed/Resolved state in a board. (Fe.: In a Scrum Board, when an issue is in the last column, JIRA burns down the story points/time estimate of that issue in its charts).

Best,

Maarten

[Sachin Dhamale]

Thanks Maarten, for clarification 

[Sajid Rahman]

Hi

I have the same situation hete. My last column is PACKAGING which is falling DONE status category only. But the difference is i have many other DONE statuses after PACKAGING..like STAGING,DEPLOYED,CLOSED all are falling under DONE status category. 

During sprint completing some of  my issues might have passed through last column PACKAGING and reached STAGING or further. In this case I'm  getting message like there incomplete issues moved to backlog. 

How to solve this issue

[Maarten Cautreels]

Hi Sajid,

So are these 4 statusses all in the same column on your board? (in the last column?) Or have you assigned the Done status category to all of them?

The second option (status category) is not understood as a "Done" status in a Kanban or Scrumboard. Only issues which are in the last column on your board will be considered done by the Scrum board.

Hope this helps.

Best,

Maarten

[Sajid Rahman]

Hi Maarteen

Thanks for your quick response!

I have only one status PACKAGING in the last column. Remaining 3 statuses not mapped this scrum board. I have another Kanban board which are having all three statuses including PACKAGING status as yhe first column.

All 4 statuses are in DONE status category

Scrum board columns will be like this:

TODO | DEVELOPMENT | TESTING | PACKAGING 

Kanban board columns will be like this:

PACKAGING | STAGING | DEPLOYED | CLOSED

My developers will complete their sprint once all the issues reached in PACKAGING status.
Then the team responsible for releasing will be taking care rest of the process. They are following Kanban process.
So as and when they receive items in the PACKAGING column they start working irrespective of the sprint. They don't wait for the sprint to complete.

Is there any way around

[Maarten Cautreels]

Hi Sajid,

Ok I see. I think you should add these three other statusses to the last column of your Scrum Board as well. This will make sure they are counted as issues that are Done once you close the sprint.

Just make sure you can't transition issues from TODO | DEVELOPMENT | TESTING to any of these 3 statusses and you won't have any problem (you can't drag issues between statusses in the same column, although you can transition them if you open the issue).

Hope this helps.

Best,

Maarten

[Daniel Marashlian]

yaaaa!!!!!!! LEGIT!

[s.weber]

Hi @Maarteen, 

is there a way to disable this? Wne when was this changed? 

In Jira we have a status category which represents "done", we have a resolution, which also represents " how it was done", and of course the wording of a status can imply the status of done.... All of this has been existing for years and has always played a role in how we have setup our workflows and so on. It also provides maximum flexibility. 

And now all of this is thrown out, and onyl the last column matters?!? Pretty strange and useless to our 60 Projects and 10k users.

I hopw we can disable this.

Thank you and BR

Sascha

[emily]

Any update on this?  It is annoying as we want to be able to close a sprint without all of our tickets that are not in the last column moving to the next sprint.  Any way to accomplish this?

[Giovanna Cóppola]

I was having the same "problem". Glad to see the solution is so simple. Thank you, Maarten!

[Chiel Schutter]

You made my day Maarten.

On-hold column was the last one...

Thanks a lot!!!!