As a Jira administrator, I frequently see this problem: child issues are closed but nobody remembered to close the parent issue. Users have already moved on to the next thing and the parent issue sits in its incorrect status forever. Or maybe it’s the opposite: the Epic is closed, but its Stories, Bugs, and Tasks were forgotten.
When issue status does not reflect reality, reporting is a nightmare. All completed or unneeded issues should be transitioned to their final status. Why not take this step off your user’s “to do” list and automate it? It’s easy to automatically transition issues with Innovalog’s Jira Misc Workflow Extensions (JMWE) app.
When all child issues are closed, automatically transition the parent so users don’t need to do it manually. Example: When all Sub-tasks are transitioned to the “Closed” status, automatically transition the Task issue to the “Closed” status.
You’ll need the following:
We’ll use the following app features:
We’ll use the following standard features:
Set up or create the following:
Here’s how to do it:
Add Transition Screen in Diagram Mode
Here’s how the workflow looks, in Text mode, with the global “Close” transition.
All statuses have a global “Close” transition.
The “Transition parent issue” behavior is the forth post function in the “Close” transition.
Finally, publish your workflow and assign it to the “Task” and “Sub-task” issue types in your Jira project.
Test your work:
The two Sub-task issues are in the “Closed” status. The parent Task issue was automatically transitioned to the “Closed” status, a resolution of “Done” was set, and a comment was added.
Why did you create a global “Close” transition instead of a single transition?
I wanted to be able to transition the Task issue to the “Closed” status from any status. If users always transition Tasks to the “In Progress” status when they start work, you could create a single transition, in the “In Progress” status, instead.
Why did you add a transition screen to the “Close” transition?
For issues with no Sub-tasks, the user needs to select a resolution value. For issues with Sub-tasks, the parent issue’s resolution will automatically match the resolution of the last Sub-task closed.
How do I automatically close Epics?
It’s not working as expected. What should I do?
Still having trouble? Check the Jira log file, turn on error handling on the Jira Misc Workflow Extensions Global Configuration page, review the JMWE documentation, review answered questions in the Atlassian Community, or raise an Innovalog support request.
Rachel WrightCommunity Leader
Last quarter, 290 developers participated in Atlassian’s annual hackathon, Codegeist, for a chance to win thousands of dollars with a new Marketplace app. We announced winners selected by Atlassian...
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