On this page



Use case

Creating repetitive issues might be time consuming work, especially when done on a daily basis. This automation rule can be used for preconfiguring sub-tasks.

Each time a new task will then be created, all needed sub-tasks will be created depending on the selected values in a checkbox field.



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!




Function

<link to function being used>

Use case descriptionWhen an issue is created, sub-tasks for each option selected in a checkbox custom field are added.
Complexity



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 in the Advanced parsing mode:

^% 
# This is a reference to each value returned by the string list



Use # to add comments in parser expressions.








Activate the rule by clicking on the Activate rule button  →



Screencast

This is how the configuration above should look on your screen


Related examples