Sub Tasks Transitions upon Parent Issues Transitioning

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

Symptoms

Sub Tasks of Parent Issues will automatically transition based on transitions by Parent Issues.

⚠️ This feature is not available in Jira by default but is achievable using a plugin/ add-on from Atlassian marketplace.

Plugin Required

The plugin/add-on you would need is called : JIRA Misc Workflow Extensions

Workaround

  1. Install the add-on from Atlassian Marketplace from your JIRA instance.

     Installing Marketplace apps

  2. Navigate to your workflow transition page for the Parent issue. Locate the appropriate status and open it. Go to the post functions tab and click on add post function.

  3. A list of additional post functions will be available from the JIRA Misc Workflow Extensions add-on.

  4. Select Transition related issues and click next

    1. Documentation for this feature can be read here: Transition related issues

  5. On the Transition(s) field , enter the relevant transition ID number or name which you want the subtask to be transitioned to.

  6. On the Which issue(s) field, select Sub-tasks of the current issue and click Add.

Success ! Your Sub-tasks will now transition to a new status based on the configuration once your parent issue is transitioned for this specific transition. Repeat the steps for other transitions if necessary.

Updated on April 8, 2025

Still need help?

The Atlassian Community is here for you.