nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Sprint cannot be completed as there are incomplete subtasks on the following issues:

Prudhvi vemulapati

Hi,

I have searched for a resolution on the community here, couldn't find a solution for my scenario.

I have a user story with 7 subtasks and all in Done status(we mark the subtasks as done once completed). But, when I try to complete the sprint I am prompted with the " Sprint cannot be completed as there are incomplete subtasks on the following issues:"

Please advise.

regards

Prudhvi

Accepted answers

Mario Carabelli

Hi @Prudhvi vemulapati

Check if the resolution of the issues us set. You can do this by using tge basic search and selecting your projrct the issue type subtask and resolution =empty

If there are issues found which are also in your current sprint then this is the reason for your problem.

You can fix this by fixing the corresponding wirkflow. A how to is found here :

https://confluence.atlassian.com/jirakb/resolutions-are-not-set-225122076.html

With kind regards

Mario

All comments

Mario Carabelli

Hi @Prudhvi vemulapati

Check if the resolution of the issues us set. You can do this by using tge basic search and selecting your projrct the issue type subtask and resolution =empty

If there are issues found which are also in your current sprint then this is the reason for your problem.

You can fix this by fixing the corresponding wirkflow. A how to is found here :

https://confluence.atlassian.com/jirakb/resolutions-are-not-set-225122076.html

With kind regards

Mario

Prudhvi vemulapati

Hi @Mario Carabelli thank you for the reply.

I identified the issue, one of the subtasks was in a different status. However, for some reason, this subtask was not displayed on the active sprints page. I could only see this in the exploded view of the user story.

Mario Carabelli

Hey @Prudhvi vemulapati

My pleasure, i am happy that i nudged you in the correct direction even if my resolution assumption was wrong.

I would appreciate if you accept my answer then for virtual glory 😉

unknown

I am having the same problem but all the subtasks on the noted tasks from the error are in a subsequent sprint, not the one I'm trying to close.

Nic Brough -Adaptavist-

Sub tasks are in the sprint that their parent is in. Are you saying that you have stories in another sprint that are showing as being in the current one?

Luke Higgins_k5wimo

I'm having this issue right now.

The same error is showing but the parent Task is in a future sprint. I can't close the current sprint.

Eugene Chin_hg79w6

same issue as Luke had. Did anyone figure why what's going on? The popup shows the current sprint has 0 open issue and all completed. then it errors out and won't close because of an issue in future sprint.

Luke Higgins_k5wimo

We've been able to mark subtasks complete, close the sprint, and then re-open the subtask.

Eugene Chin_hg79w6

I guess that's a good trick to work around this.

I have found another issue with cloned subtask. if I run a filter for project = blah and sprint = 3 or something all issues other than subtasks shows up but the cloned subtasks also got mixed in there which is weird. anyway, seems like cloned subtasks just keep some weird state information in there that doesn't get updated. I will just be no lazy and manually type in all the info and restrain from cloning subtasks.