Automation for Jira - How to automatically close sub-tasks from a parent issue

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


When a Jira issue (for example a story) has multiple sub-tasks underneath it, it might be tedious to close each sub-task 1 by 1 after closing the story.

Not closing the sub-tasks linked to a Story might prevent Jira users from closing a Sprint, since Sprints require all issues (including their sub-tasks) to be closed, as explained in the feature request JSWSERVER-12012 -[ Unable to close Sprint with closed parent issue and open sub-tasks] This knowledge article provides an example of an automation rule that automatically closes all the sub-tasks of a parent issue after the parent issue is closed.


The automation rule can be configured as described below:

Automation rule configuration

  • When: Issue transitioned

    • From status: Any status

    • To: Done (Feel free to change this status to the one that matches your workflow)

  • Branch rule / related issues:

    • Type of related issues: Sub-tasks

  • Then: transition issue (to place inside the branch)

    • Transition the issue by Selecting the destination status

    • Destination status: Done (Feel free to change this status to the one that matches your workflow)

The screenshot shows the full rule

Automatically close sub-tasks from a parent issue using automation for jira

Updated on June 7, 2024

Still need help?

The Atlassian Community is here for you.