Automation for Jira - How to automatically close an Epic once all its child issues are closed
Platform notice: Server and Data Center only. This article only applies to Atlassian products on the Server and Data Center platforms.
Support for Server* products ended on February 15th 2024. If you are running a Server product, you can visit the Atlassian Server end of support announcement to review your migration options.
*Except Fisheye and Crucible
Summary
The purpose of this article is to provide a way to configure an automation rule that will automatically close an Epic once all its child issues (stories, tasks, etc.) are closed.
Environment
- Jira Server / Data Center 8.0.0 and any higher version
- Automation for Jira 7.4.0 and any higher version
Solution
Automation rule configuration
New Trigger: Issue transitioned
- From status: leave blank
- To status: Done
Make sure to change the status to the one used in the workflow when an issue is closed (for example: Closed, Resolved, etc...)
Branch Rule / related issues
- Type of related issues: Epic (parent)
- Rule restricted to projects: <Your project name here>
In the Branch:
New Condition: Related issues condition
- Related issues condition: Stories (or other issues in this Epic)
- Condition: All match specified JQL
- Matching JQL: status = Done
Make sure to change the status to the one used in the workflow when an issue is closed (for example: Closed, Resolved, etc...)
- Rule restricted to projects: <Your project name here>
New Action: Transition issue
- Transition the issue by: Selecting the destination status
- Destination status: Done
Make sure to change the status to the one used in the workflow when an Epic is closed (for example: Closed, Resolved, etc...)
Screenshot of the automation rule
