On this page



Use case

When a story is approved, two sub-tasks for Development and QA will be created.



Configuration steps


Mode*

Choose Multiple issues based on a text list.

Expression

["Development","QA"]

with parsing mode set to General.

The number of list elements defines the number of issues to be created.



Issue type*

Choose Selected issue type and Sub-task as its value.


The issue type to be created is being set to Sub-task.



The issue type must be present in your system.



Parent issue*

Select current issue.


The sub-task will be created under the current issue .




Summary*

Insert the following expression:

%{seed.text} of %{issue.key}



A generic summary indicating the purpose of the sub-task.




Description

Insert the following expression:

This sub-task was automatically created because the Story and parent issue %{issue.key} has been approved.
In case doubts or concerns do not hesitate to contact [~accountid:%{system.currentUser}].



The description links to the current issue key.



The syntax used for the mention guarantees that a working user mention is added to the comment regardless of personal Atlassian account settings of the mentioned user.



Run as*

Choose which user* will be able to execute the post function. By default, it is set to the Current user.


Conditional execution

Insert the following expression using the parser mode "Logical":

%{issue.issueType} = "Story"


The sub-task will only be created if the current issue (parent) is a Story.





Related examples



JWT feature

Workflow functionCreate issue
Parser functions
Label
Use case description

When a story is approved, two sub-tasks for Development and QA will be created.

Complexity