Use case
Creating multiple sub-tasks when a field in an issue is updated with a certain value would be very time-consuming, especially if the number of sub-tasks is not constant. By following the steps below, you can automate your sub-tasks creation and spare time!
Should I use a workflow post function or an automation rule?
When to use this workflow post function and when to use an automation rule?
This use case is very useful if only want to create issues automatically for one project and workflow.
If repetitive issues have to be created in several projects, however, that have different workflows, configuring just one automation rule with the Create issue action might then be the easier way to go.
In this case, you might want to check out our corresponding automation use case.
⚒️ Configuration
Add a Create issue post function to the workflow transition you want. The Create issue transition might be the best choice here.
Issues to be created
Mode
Choose Multiple issues
Expression
subtasks(linkedIssues())
with parsing mode set to Issue list
Issue type
Choose Parser expression (sub-task issue type)
Expression
%{seed.issue.issueType}
Parent issue
Choose Current issue
Summary
Enter the following Parser Expression :
%{seed.issue.summary}
with parsing mode set to Basic text.
Description
Enter the following Parser Expression :
%{seed.issue.description}
with parsing mode set to Basic text.
Conditional execution
Enter the following expression:
%{issue.cfnnnnn} = "Value"
Replace nnnnn with your field code and " Value " with your field value.
Run as
User
Choose Current user
