On this page
Use case
When an issue is created, sub-tasks for each option selected in the 'Checkbox' custom field are added.
When to use this automation rule and when to use a workflow post function?
This use case is very useful, if repetitive issues have to be created in several projects that have different workflows. Configuring just one automation rule might then be the easier way to go. But if this scenario is only necessary for one project and workflow, the Create issue post function would make more sense. In this case you might want to check out our corresponding post function use case.
Need always the same issues to be created?
No problem! Just take a look at this use case!
Issue Event
Create a new rule and name it appropriately.
Providing a description will help you to identify what the rule does but this step is optional.
Add a trigger and choose the Issue event → Issue created
Create Issue
Add Action → Create Issue
Issues to be created*
Choose Multiple issues
Parser Expression*
toStringList(%{trigger.issue.cfnnnnn})
with the Parsing mode set to String List
Note that: nnnnn is field code for the checkbox custom field.
Issue type*
Choose Sub-task
Parent issue*
Choose Trigger issue
Summary*
Use the following parser expression win the Advanced parsing mode.:
^% #This is a reference to each value returned by the string list
Activate the rule by clicking on the Activate rule button →
Screencast
This is how the configuration above should look on your screen
Related examples
If you still have questions regarding this example or others, feel free to refer to our support team.