How to create multiple issues - advanced example


This builds off of How to create multiple issues and is part of release 3.3. This can be used to create subtasks or issues, the example here will be for subtasks. Advanced techniques are used to show:

  1. Creating issues based on information in the original issue that caused the transition - for example, creating a subtask for each version listed as a fix version.

  2. Subsetting the information to exclude some entries.

  3. Controlling duplication of issues when the same transition is done again. 


  1. Follow the steps similar to How to create multiple issues

  2. Determine the field in the original issue that will control the number of issues to be created. For instance, this could be one of the many Substitution variables that produce a comma-separated list like original_fixed_versionsrole_developersoriginal_labels_comma_separated, or similar.

  3. Determine any include or exclude criteria for subsetting the entries to be considered.

  4. Determine if duplication prevention is needed and, if so, determine a condition that could be used to determine if the create should proceed. A JQL query is a convenient way to do this.

  5. Configure the post function - see the example.

Example - Fix versions


Quote fix version fields that may contain blanks

Use "%entry%"

What happens when there are no fix versions?

If the Create multiple issues field is replaced with blank or the regex eliminates all candidates, then no issues will be created.

How to debug your scenario

How to get problem determination information shows you how to get information about what is happening on the transition.

Example - Setting unique values for other fields

Create multiple subtasks on transition that have different assignees discusses some of the techniques that can be used. Provide substitution variables for custom field option values provides the basic enablement for this.