Futures used to implement the example
Example: Create multiple subtasks with different summaries
In this example multiple subtasks should be automatically created with different summaries when creating a new issue.
For example:
Creating issue "Release x.y.z" should automatically create subtasks
- "Documentation for Version x.y.z"
- "Blog entry for Version x.y.z"
- "Newsletter for Version x.y.z"
- "Social Media for Version x.y.z"
The configuration will look like this:
Text to be parsed is:
getMatchingValue(^,[1,2,3,4],
["Documentation for Version " + %{00074},
"Blog entry for Version " + %{00074},
"Newsletter for Version " + %{00074},
"Social Media for Version " + %{00074}])
Note that:
- %{00074} is field code for Fix Versions
Once configured, the transition will look like this:
The created issue will look like this:
BITTE DIE MAKROS UM NAME DER POST FUNCTION (LINKES MAKRO) UND WEITERE LABELS (RECHTES MAKRO) ERGÄNZEN UND HIER DIE SECTION LÖSCHEN!
HIER DIE SEITE DANN BITTE AUCH UM JEWEILIGE LÄBELS ERWEITEN!
Other examples of that function
- Assign new issues to a different project role depending on field value in current issue
- Clone an issue and all its subtasks (with additional restrictions)
- Create 3 issues in 3 different projects
- Create a dynamic set of sub-tasks based on checkbox selection with unique summaries
- Create a static set of sub-tasks with unique summaries
- Create a story for each component in an epic
- Create a sub-task for each user selected in a Multi-User Picker
- Create a sub-task in each story of an epic
- Create specific sub-tasks for each selected component