---
title: "How to create multiple issues - advanced example"
canonical: "https://support.appfire.com/space/SUPPORT/89135679/How%20to%20create%20multiple%20issues%20-%20advanced%20example"
format: markdown
---
# Description

This builds off of [How to create multiple issues](https://appfire.atlassian.net/wiki/spaces/SUPPORT/pages/89135528) and is part of [release 3.3](https://appfire.atlassian.net/wiki/spaces/CSOT/pages/68772258). 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 [How to create multiple issues](https://appfire.atlassian.net/wiki/spaces/SUPPORT/pages/89135528)
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/spaces/SUPPORT/pages/89139918) 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

> Macro (section)
> 
> > Macro (legacy-content)
> 
> > Macro (legacy-content)

> ✅ **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](https://appfire.atlassian.net/wiki/spaces/SUPPORT/pages/89136042) 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](https://appfire.atlassian.net/browse/CSOT-102) discusses some of the techniques that can be used. [Provide substitution variables for custom field option values](https://appfire.atlassian.net/browse/CSOT-103) provides the basic enablement for this.