Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

Cannot complete sprint as it shows subtasks are incomplete, but these subtasks are in another sprint

I'm trying to complete the current sprint, but I'm getting message saying that "Sprint cannot be completed as there are incomplete subtasks on the following issues: +list of subtasks".
Actually these subtasks and corresponding stories are in the next sprint (checked it twice). Tried to change dates in the current sprint or move stories to the backlog, but it's still the same.
Could you please help me to solve this problem?

Kind Regards,

1 answer

0 votes

Your initial question "subtasks are incomplete, but these subtasks are in another sprint" made me think that there's an easy answer - "no, the subtasks are in the same sprint as their parent issues, by definition, they can't be in another sprint", but this looks a bit more complex than that.

Forget the subtasks for a second.  Can you get a definitive list of what is currently in the sprint at the story level?  Either check the sprint in the backlog view, or, better, run a search for "sprint = <sprint name>".  This will give you a list of the current stories.

Then check this against the list of issues it's giving you in the "incomplete issues" list

I suspect you'll find that the list of issues that are incomplete are:

  • In the current sprint you are trying to close
  • In the last column on the board (the column Jira recognises as done)
  • Have one or more open sub-tasks (not in the last column)

If that is the case, then you've put Jira into a situation it needs your help understanding.  You are telling it that these stories are done, but not done, at the same time, and Jira needs to know which one it is before it can close the sprint.

If a story has an open sub-task (which is a part of it), then logically, it cannot be complete, because a part of it is not.  But you've marked the story complete.

Solution is to move all the sub-tasks into the done column, OR re-open the story - move it back to any other column. 

@Nic Brough _Adaptavist_ , thank you for the quick answer!
I did checked every single issue from the notification separately and in the backlog view - these issues are definitely in the next sprint and some of the even in the backlog. I checked subtasks in these issues - they belong to the same sprint as the parent issue.
Screenshot 2022-05-19 at 12.36.11.pngScreenshot 2022-05-19 at 12.36.47.png

Had to close all the subtasks to close the current sprint and reopen them after starting the new sprint. 
It worked, but took too much time.

Suggest an answer

Log in or Sign up to answer

Community Events

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

Find an event

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

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you