0 issues were Done when completing Sprint


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...



3 answers

1 accepted

8 votes
Accepted answer
Maarten Cautreels Community Champion Nov 26, 2013
First thing that comes to mind: did you configure the Closed status to be the last column in the status columns?

Hi Maarten, 

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

Maarten Cautreels Community Champion Jun 01, 2017

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).



Thanks Maarten, for clarification 


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 Community Champion Jun 06, 2017

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.



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:


Kanban board columns will be like this:


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

Like 1 person likes this
Maarten Cautreels Community Champion Jun 07, 2017

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.



Like 1 person likes this

yaaaa!!!!!!! LEGIT!

Like 1 person likes this

You made my day Maarten.

On-hold column was the last one...

Thanks a lot!!!!

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

Suggest an answer

Log in or Sign up to answer
Community showcase
Published 16 hours ago in Jira

How you can achieve compact and easy-to-maintain workflows in your JIRA( Server)

This approach requires you to have the JIRA administrative rights. The main aim of this article is to help you achieve an organized, easy-to-maintain workflows in your JIRA instance thereby, reducin...

151 views 0 0
Read article

Atlassian User Groups

Connect with like-minded Atlassian users at free events near you!

Find a group

Connect with like-minded Atlassian users at free events near you!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you