Prior to version 3.3, in order to create multiple issues or subtasks, you needed to configure a Create issue or Create subtask post function for each issue to be created. Version 3.3 adds an option to make it easier to create multiple similar issues (or subtasks) with one post function. Multiple post functions can still be used and may be needed for creating issues with unique settings or to use different conditioning. Also see: How to create multiple issues - advanced example.
- Choose to add the Create issue or Create subtask post function as usual.
- Configure various options as usual.
- Find the Create multiple issues parameter.
- Add a comma separated list of entries. Processing will:
- Look at each entry
- If no pattern is provided, the entry will be selected for continued processing
- If a pattern is provided, then processing will continue only if the entry matches the selection criteria provided by the regex pattern and qualifiers provided
- Each selected entry will then drive the potential creation of the issue or subtask based on conditioning and the other parameters provided
Example - Simple
The following configuration will create 2 new issues when the transition is activated. One will be assigned to tom and one will be assigned to sally.
- Set multiple issue value field to: tom, sally
- Set the assignee field to: Specific user with the specific user field set to: %entry%
- Save and publish
You can do a similar thing for any other field. To demonstrate, lets assume you set the summary field to: Issue for %entry%. Because there are 2 entries in the comma separated list (and no additional filtering defined), 2 issues are going to be created each with a different summary.
|1||tom||First issue created||Issue for tom|
|2||sally||Second issue created||Issue for sally|
There are many ways to get a comma separated list of values. The simple example above just uses a hardcoded list, but the more interesting use cases are using Substitution variables to create the list. For example:
- Using results of a JQL query to create an issue for each issue found - see How to create multiple issues - advanced example
- A checkbox custom field - creating an issue for each selected item
- A select list custom field - creating an issue for each selected item
- Fix or affects version field - creating an issue for each version
- Components field - creating an issue for each component