Create multiple subtasks for specific issue type - Cloud

Create multiple subtasks for specific issue type - Cloud

Scenario

Each time a new issue is created that is of a certain issue type, you want to create a set of sub-tasks using the same summary as the parent issue.   

Background

We can configure a Create Sub-task post function that processes when users create a new issue. For each instance of this transition, we inspect the issue type and if it is a "Story", we automatically create a set of sub-tasks. We inspect the issue type using one of Create on Transition's powerful Substitution Variables. In order to better identify subtasks, we prepend the parent issue summary with the name of the sub-task.

Steps

The following steps demonstrate how to configure Create on Transition, using regex inspection of the issue type and the Create multiple issues feature:

Step 1

As a Jira Administrator or Workflow Administrator:

  1. Click the Cog icon to open the Settings menu and select Issues

  2. Click Workflows

  3. Navigate to your workflow and edit your workflow to create a draft version

  4. Select step 1

  5. Select Create transition

  6. Select the Post Functions tab.

  7. Click Add post function

  8. Select Create Sub-task (Bob Swift) post function and add

Step 2

Within the Issue Fields screen:

  1. Select the Basics Fields tab

  2. Prepend "@entry@ - " to "%parent_summary%" in the Summary field to get the Sub-task's name in the Sub-task's Summary.

Step 3

Define the regex used to inspect the issue type of the parent issue and the exact matching condition that is used to evaluate. Also, configure the Create multiple issues field using a substitution variable.

  1. Select the Conditions & Configuration tab.

  2. Enter "%original_issuetype%" in the Condition 1 field.

  3. Enter "Story" in the Regular expression pattern field.

  4. Select Exact matching condition, so we only create the sub-tasks when the issue type is "Story".

  5. Scroll down until you find Create multiple issues.

  6. Enter "Development, Testing, Documentation".

  7. Click the Add button to save your configuration.

Step 4

  1. Ensure to publish your workflow. It is always recommended to save a backup of the previous workflow when prompted.

  2. Create an issue of type "Story".

  3. Validate that the new sub-task issues were created and that it contains the name prepended before the parent summary.

 

 

Need support? Create a request with our support team.

Copyright © 2005 - 2025 Appfire | All rights reserved.