-
Suggestion
-
Resolution: Unresolved
-
None
-
5
-
9
-
Problem Definition
When attempting to close a sprint, you may see an error preventing the closure due to the subtasks being in a state that differs from their parent.
Suggested Solutions
- An option to make this not required to close a sprint
- A wizard to prompt you to correct the board configuration as a means to adjust this
Why this is important
It has become commonplace for subtasks to utilize different workflows from other work/issue types. It is also common to not see subtasks on all boards, which further restricts a user that might have permissions to close the sprint normally to be able to adjust and correct for this error. Both conditions can cause this behavior to be exhibited.
Workaround
See knowledgebase article in https://support.atlassian.com/jira/kb/sprint-cannot-be-completed-as-there-are-incomplete-subtasks-in-jira-cloud/ as this explains there are two different scenarios in which this can happen, and for steps to workaround this.
Subtasks do not have the same lifecycle as user stories. So it stands to reason that the statuses for a subtasks will not always be the same as for user stories.
However JIRA won't let me close a sprint unless the subtasks of user stories have a status that's the same as one of the statuses of the user story itself.
For example, say I have a user story workflow of Ready | In Progress | Ready for QA | In QA | In Review | Done. That's fine.
Then say I create a subtask workflow of To Do | In Progress | Approved | Closed.
If I have any stories which have subtasks in a state of "Approved" or "Closed," JIRA will not allow me to close the sprint. Instead I get the message, "Sprint cannot be completed as there are incomplete subtasks on the following issues:"
This is bizarre. Why allow people to modify workflows for different issue types and subtypes if this then prevents the valid closing of a sprint?
- relates to
-
- Gathering Interest