Jira wants to move COMPLETED stories to the backlog upon sprint completion?

My team finished our first sprint using JIRA Agile on the 14th.  We had failed to complete two stories, and so I moved those into the next sprint.  Three stories remained on the backlog, and all of the stories (and all of the tasks in each story) had been marked as "Done."  However, when I try to complete the sprint JIRA indicates that there are 3 incomplete stories that will be moved to the backlog.

How do I indicate that the stories are complete?  Again, I have marked each and every sub-task and story with the status of "Done."  I'm not sure what else to do.

finished story.PNG

Here you can see that the story and the sub-tasks are all "Done" (the names are crossed out).

cannot complete.PNG

But when I try to complete the iteration I am told that ZERO issues are complete and 3 will be moved to the backlog.  Help!

2 answers

1 accepted

1 vote
Accepted answer

What column are they in on your scrum board?  The resolution/strikeout doesn't really matter when it comes to ending a sprint, the question is what column they are in.

task board.PNGThey are in the "Done" column.  

The agile board will only deem "completed" the items on the rightmost (green) column (no mater what you do or how you call it) regardless the workflow.

To work it around you may move your "impeded" (* ) column somewhere in the middle of the flow. Not quite elegant indeed.


(* ) We use "flags" to flag impediments instead.

I found this similar problem: https://answers.atlassian.com/questions/238073

 The major differences seem to be:

  1. I am using Epics/Stories/Sub-Tasks rather than vanilla JIRA Issues.
  2. When I try to configure my task board (as the comments on the above question suggested) to add a new status to one of the columns, the only options I see are "To Do," "In Progress," "Done," and "Impeded."  There is no option to include a "Closed" status (unless I make a custom one with that name, but that's obviously not the same thing).

One of my colleagues has a separate JIRA Agile instance that he's using, and his "Done" column has two statuses by default: "Done" and "Close Issue."  When he drags a task or story into the "Close Issue" area of the "Done" column the issue is marked as CLOSED and he is not seeing this problem.  


It was absolutely the column order that was causing the problem.  Moving the "Done" column into the rightmost position (with "Impeded" in the middle) immediately helped JIRA to recognize that the "Done" tasks were completed.  Thanks for the help, folks.

What a saving grace this answer has been!

Suggest an answer

Log in or Sign up to answer
Community showcase
Published Jan 29, 2019 in Jira Software

Transforming Jira Software projects for general project management purposes

...It's true that there are projects in Jira; but they are merely a way to cut off issues, to tell them apart from other sections of work and to apply rules that are specific to that team (the schemes)....

206 views 0 6
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