Can't close sprint due to cloned tasks

Fraser Coleman

Twice now I have been unable to close a sprint due to 'incomplete subtasks'  the issue is these sub-tasks are in tasks that aren't even in Done (so not the usual reason).  So trying to move them into the next sprint and yet it's blocking sprint closure.

This most recent time, the sub-tasks in question aren't even in the sprint, i.e. cloned task in sprint 9, and put it into sprint 10.  Can't close sprint 9 because of sub-tasks in a ticket in sprint 10?

I have tried removing the 'clone' link. Didn't help.  The only way I could resolve it was by moving the offending ticket to the backlog. closing sprint 9, then moving the tickets back to sprint 10.

This doesn't seem quite right.

Petter Gonçalves

Hello @Fraser Coleman

Welcome to the Atlassian Community!

Per your description, I understand that you are not being able to close your Sprint because some sub-tasks from another Sprint (which parents also are in a different Sprint) are not complete, while the only relation is that these sub-tasks were cloned from sub-tasks that are currently in the Sprint you are trying to close. Is that correct?

I just would like to double confirm with you if ALL the Parents of the incomplete sub-tasks are not in the current Sprint (Sprint 9). Can you confirm that?

Also, I see you flagged this issue as Next-gen. Can you confirm if that's the project template you are using?

Checking the details you provided so far and considering that you are using a Next-gen project, I believe you might be facing the following bug:

Cannot complete a sprint in a next-gen project if an issue added to a sprint is converted from Task to Subtask. 

By default, Jira always copies the Sprint reference from the parent issue to its sub-tasks. The mentioned bug causes Jira next-gen to keep the reference from the previous Sprints in the Sprint field when converting parent issues to sub-tasks, not updating with the current parent Sprint.

Additionally, there a few other resolved bugs that caused the same behavior when cloning or even moving sub-tasks from one parent to another, so we would need further investigation on the logs to understand if this could be a rollback of one of those bugs.

Anyway, to confirm if this is the behavior you are facing, please run the following JQL in your issue navigator and check if the sub-tasks that are causing the error are returned in the query:

Sprint = "Sprint 9" and issuetype = Subtask

P.S: You can use the "Status" column to easily find open issues on the query.

If the sub-tasks are indeed pointing in the wrong Sprint (Different from their Parent issues), please open an internal ticket with us so we can further investigate what happened and properly fix this incoherency in the background:

https://support.atlassian.com/contact/ 

Let us know if you have any questions.