Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

I'm unable to close my sprint due to open subtasks in a team-managed project

Carrie Curtner
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
May 30, 2025

I'm unable to close a sprint on a team-managed board due to open subtasks included in the sprint; however, the flagged parent work items and all their subtasks are all in "done" statuses (most "done," some "won't do). 

I've done a filter search for any unresolved work items, including subtasks, in the sprint. I've logged out of jira and back in again, in case it's a caching issue. 

One other thing to note, did start the next sprint when I couldn't get unblocked on closing the old sprint, which I understand might have me in even more of a bind when it comes to closing the old sprint, but here we are. 

1 answer

1 accepted

3 votes
Answer accepted
Trudy Claspill
Community Champion
May 30, 2025

Hello @Carrie Curtner 

Welcome to the Atlassian community.

Are the parent issues and their subtasks all assigned to Statuses that are mapped to the column farthest to the right on the scrum board?

Regardless of the actual value of the Status or the Resolution field, only the issues assigned to Statuses that are mapped to the column farthest to the right on the board will be considered "complete" at the end of the sprint. If the issues are in a status that is in a different column they will be considered "incomplete".

Carrie Curtner
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
June 1, 2025

Ah, okay. I think I've been confused about the separation between status mapping and column configuration. So, it's possible to have multiple statuses that resolve an issue, but in order for those status values to allow you to close out a sprint, the statuses have to be mapped to a single column, because it's not possible to have two right-most columns. So the trade off is I lose the ability to separate my won't dos from my dones on that actual board layout, which isn't the end of the world, and if I really cared about being able to see my won't dos at a glance, I could just do a filter view on the board. 

This isn't intuitive, but at least I understand now. Thanks for your help. 

Like Trudy Claspill likes this

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
PREMIUM
PERMISSIONS LEVEL
Product Admin
TAGS
AUG Leaders

Atlassian Community Events