On this page
Use case
When a story is approved, two sub-tasks for Development and QA will be created.
Configuration steps
First sub-tasks "Development"
Issue type*
Choose Selected issue type and Sub-task as its value.
The issue type must be present in your system.
Parent issue*
Select current issue.
Summary*
Insert the following expression:
Development of %{issue.key}
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 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.
Second sub-task "QA"
Issue type*
Choose Selected issue type and Sub-task as its value.
The issue type must be present in your system.
Parent issue*
Select current issue.
Summary*
Insert the following expression:
QA of %{issue.key}
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 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:
%{issue.issueType} = "Story"
The sub-task will only be created if the current issue (parent) is a Story.
Related examples
Use case |
---|
No content found. |
If you still have questions, feel free to refer to our support team.