---
title: "Create multiple issues - advanced example"
canonical: "https://support.appfire.com/space/CSOT/1916305680/Create%20multiple%20issues%20-%20advanced%20example"
format: markdown
---
> Macro (aura-html)

# Description

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.

# Steps

1. Follow the steps similar to [create multiple issues](https://appfire.atlassian.net/wiki/x/CQFWg)
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](https://appfire.atlassian.net/wiki/x/bRQZB) that produce a comma separated list like **original_fixed_versions**, **role_developers**, **original_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

|  |
| --- |
| Use **"%entry%**" |

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