Automation for Jira - How to automatically close an Epic once all its child issues are closed

Platform Notice: Data Center Only - This article only applies to Atlassian products on the Data Center platform.

Note that this KB was created for the Data Center version of the product. Data Center KBs for non-Data-Center-specific features may also work for Server versions of the product, however they have not been tested. 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.

Solution

Automation rule configuration

New Trigger: Issue transitioned

  • From status: leave blank

  • To status: Done

When an issue is closed, make sure to change the status to the one used in the workflow (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

When an issue is closed, make sure to change the status to the one used in the workflow (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...)

 How to automatically close an Epic once all its child issues are closed

Updated on June 7, 2024

Still need help?

The Atlassian Community is here for you.