Cannot close a sprint with stories that are resolved that have tasks that are closed.

When I try and close a sprint some people have marked tasks as closed. 
This stops me finshing the sprint unless I move all the tasks to resolved.

I don't care if tasks are closed or resolved. How can I force the sprint to end? 

2 answers

1 accepted

This is described here: https://confluence.atlassian.com/display/AGILE/Ending+a+Sprint 

Any issues not completed at the end of the sprint will be moved to the next planned sprint, as they did not meet the team's definition of "Done". If you do not have a next planned sprint, they will be returned to the backlog and will be visible in the Backlog of the board.

  • If you have parent issues that are not 'Done' but have sub-tasks that are all 'Done', the parent issues will still be moved to the next sprint/backlog. If these parent issues are part of another active sprint, the previously completed sub-tasks will still be 'Done'.  

 

Sorry nope. The parent is resolved (ie done and should not be moved to the next sprint) just it has some subtasks that are marked "Closed" so jira throws a fit. I suppose jira is not recognising that Resolved and Closed are 'done'. How do I tell jira that resolved and closed are both 'done'

You have to check out your workflow; Resolved != Closed by Jira default settings. This is the standard comment for Jira's resolved: "A resolution has been taken, and it is awaiting verification by reporter. From here issues are either reopened, or are closed." Change the workflow to suit your need, or have the team explicitly set the issues to closed when you're first at it.

But the problem is when things are marked as closed jira won't let the sprint complete... You are suggesting something has got misaligned from default jira install? We have done very little customisation

No, I'm saying that this is default Jira behavior. Resolved != Closed. If you want to get Resolved == Closed, you have to change the workflow.

Thank you very much for your attempts to help me. I find the internals of jira frustrating and confusing! Can you point me to where or how I need to change the workflow? I cannot see what jira looks at in the closing of a sprint to make its decisions.

You are now entering an area that can be confusing; I suggest you read up before you progress. Start with https://confluence.atlassian.com/display/JIRA/Configure+workflows+and+screens. The look at https://confluence.atlassian.com/display/JIRA/Configuring+Workflow. Yes, the internals of Jira can be confusing. But the upside is the possibilities you have to configure it according to your needs.

(╯°□°)╯︵ ┻━┻

Hi AW,

I had exactly the same problem. If you haven't already found the solution, take a look at https://answers.atlassian.com/questions/9867148/jira-wants-to-move-completed-stories-to-the-backlog-upon-sprint-completion.

Simple solution in the end (but oh so infuriating to track down)

Suggest an answer

Log in or Join to answer
Community showcase
Sarah Schuster
Posted Jan 29, 2018 in Jira

What are common themes you've seen across successful & failed Jira Software implementations?

Hey everyone! My name is Sarah Schuster, and I'm a Customer Success Manager in Atlassian specializing in Jira Software Cloud. Over the next few weeks I will be posting discussion topics (8 total) to ...

2,755 views 11 18
Join discussion

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
Atlassian Team Tour

Join us on the Team Tour

We're bringing product updates and pro tips on teamwork to ten cities around the world.

Save your spot