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

# Scenario

You want to create multiple issues using the `Create Issue` or `Create Sub-task` post function.

## Background

For each new hire, automatically create an issue for each application or resource the user needs.

# Steps

<span style="color: #333333">The following steps demonstrate how to configure Create on Transition for Jira so it automatically creates issues:</span>

## Step 1

As a Jira Administrator or Workflow Administrator:

1. Click the **Cog** icon to open the *Settings* menu and select **Issues**.
2. Click **Workflows**.
3. Navigate to your workflow and edit your workflow to create a draft version.
4. Select the transition.
5. Select the *Post Functions* tab.
6. Add a `Create Issue` or `Create Sub-task` post function.

## Step 2

**Optional rules**

1. Select the *Conditions & Configurations* tab.
2. Scroll until you find *Create multiple issues*.

![image-20260828-122430.png](media://4d283f20-3d4a-483e-aa25-23d153893b2d)

### Filter the list with a regular expression

Configure filtering using two fields, in the same layout as *Condition 1*:

| **UI field** | **What to enter** | **Purpose** |
| --- | --- | --- |
| **Create multiple issues** | Source list (comma-separated values or a substitution). | Entries to evaluate: one issue may be created per matching entry. |
| **Regular expression pattern** | Regex pattern (optional). | If set, only entries that match the pattern are used. |
| **Exact** (checkbox) | Optional. | Pattern must match the entire entry (not just a substring). |
| **Literal** (checkbox) | Optional. | Treat the pattern as plain text, not a Java regex. |
| **Negative** (checkbox) | Optional. | Exclude entries that match (instead of including them). |

> ℹ️ Enter the source list and pattern in separate fields. Don't type `%function_filterList(...)%` into **Create multiple issues**. Use the **Regular expression pattern** field instead.

#### Example (filter components)

Your issue has components `zValidation - Channel`, `zValidation - Servo`, and `zVerification - Servo`.

| **Field** | **Value** |
| --- | --- |
| **Create multiple issues** | `%original_components%` |
| **Regular expression pattern** | `zValidation` |

**Result**: Issues are created only for the two `zValidation` components; `zVerification - Servo` is skipped.

Use `@entry@` in **Summary** (or other fields) so each created issue uses the matching component name, as described in Step 3.

## Step 3

**Issue fields**

Dynamically assign the issue using a substitution variable called `@entry@`, and use that same variable to append the user to the summary so you can differentiate each issue created.

1. Select the *Detailed Fields* tab.
2. Locate the **Assignee** field under the *People* section.
3. Enter `@entry@`.
4. Select the *Basic Fields* section.
5. Locate the **Summary** field. You see `%parent_summary%`.
6. Append `- @entry@` to `%parent_summary%`.
7. Click **Add** to save the values.

## Step 4

1. Publish your workflow. We recommend saving a backup of the previous workflow when prompted.
2. Create a *Task* issue.
3. Validate that the new issues or sub-tasks were created and properly assigned.