On this page



Use case

This use case serves the purpose of giving a detailed explanation on how to create several sub-tasks depending on the component or components in the Components field.


Configuration



Add a Create issue post function to the workflow transition of your choice.



Issues to be created

Mode

Choose Multiple issues.


Expression

Write an expression using this format with parsing mode in Text list.

("Component A" in %{00187} ? ["A1", "A2", "A3"] : []) APPEND
("Component B" in %{00187} ? ["B1", "B2"] : []) APPEND
("Component C" in %{00187} ? ["C1", "C2", "C3", "C4"] : []) APPEND
("Component D" in %{00187} ? ["D1"] : [])


In this expression we check that every defined component is in the Components field and, if it is, we add the texts between quotation marks to a text list. The number of elements in the resulting list defines the number of issues to be created.



Issue type

Choose Selected issue type.


Specific issue type

Choose Sub-task.


Parent issue

Choose Current issue.




Summary

Enter the following expression 

"Sub-task of %{issue.key} - " + %{seed.text}

with parsing mode set to Advanced text.

The texts of the text list of the previous expression will replace in each newly created sub-task the seed text field code.



Description

To enrich the issue with further information, you might want to add a short description, although it is not mandatory.





Related use cases



JWT feature

Workflow function

Create issue

Parser functionsLinks to all used parser expressions. Enter links separated by a blank space
Labelused to mark a use case as staff pick





Status
Tech review

Style guide