Using the Create subtask workflow post function allows you to create one or more subtasks when the post function is processed after a workflow transition step. The configuration of this post function is streamlined by grouping all configuration settings into various tabs for easy access:
ISSUE FIELDS - Allow you to define the contents of one or more fields when a subtask is created by this post function. Substitution variables can then be used to populate fields. Issue Fields are grouped into the following common categories:
Basic Fields - includes fields that are most commonly used when creating a new subtask in Jira.
Detailed Fields - includes details associated with the sub-task, people involved, and dates.
Links - includes details of subtask links and link types.
Comments & attachments - includes details about how you want to handle comments and specifics associated with attachments.
Custom Fields - controls whether to copy custom fields and allows you to define values for new custom fields.
OPTIONAL RULES - Allow you to define the additional criteria for when and how to create the subtask(s). Optional Rules are grouped into the following category:
Conditions & configuration - Define one or more conditions for when to create the subtasks(s), use JQL to define substitution variables to be used to populate other fields, and set the acting user for the subtask creation.
HELP - Provides quick links to troubleshooting and additional documentation
When you create multiple post functions to create multiple subtasks, these post functions are run in parallel during transition. Once the sub-tasks are created for the configured workflow transition, you may notice that the sequence of subtasks' issue numbers is different from the sequence of the Create subtask post functions added during configuration. This is because the order of the subtasks created after transition is dependent on the time taken to complete each of these post functions.