---
title: "Create issue if transitioned by specific user - Data Center"
canonical: "https://support.appfire.com/space/CSOT/68749642/Create%20issue%20if%20transitioned%20by%20specific%20user%20-%20Data%20Center"
format: markdown
---
> Macro (aura-html)
# Scenario
You would like to create an issue only in the case where it was transitioned by a specific user.
## Background
This scenario uses an example [ePub workflow](https://bobswift.atlassian.net/wiki/download/attachments/443875364/ePub-workflow-diagram.png?version=1&modificationDate=1521470932712&cacheVersion=1&api=v2) that helps teams coordinate the publication of electronic books. We can add a Create Issue post function that processes when users transition issues from the "In Edit" to "In Composition" steps and uses regex to inspect a built-in [Substitution Variable](https://appfire.atlassian.net/wiki/x/bRQZB) called "%transition_user_id%". If the user transitioning matches the value(s) provided, then a new issue is created. If the user does not match, a new issue is not created, but the transition step is processed.
## Steps
The following steps demonstrate how to configure Create on Transition, regex inspection of the user transitioning using a built-in function:
| | | |
| --- | --- | --- |
|  | ## Step 1
As a Jira Administrator or Workflow Administrator:
1. Navigate to your workflow (ePub in this case).
2. Edit your ePub workflow to create a draft version.
3. Navigate to the Post Functions tab.
4. Add a *Create Issue* post function. |  |
|  | ## Step 2
1. Navigate to the *Conditions & Configuration* tab.
2. Enter "%transition_user_id%" in the *Condition 1* field.
3. Enter the name(s) you would like to match within the *Regular expression pattern* field.
In this case, we would like to search for any of the three ("bsmith|tlee|jjones").
Using the pipe "|" between values indicates an OR condition (e.g., bsmith or tlee or jjones).
4. Select the *Exact* match check box to the right, so you only return on exact username matches.
5. Click the **Add** button to save your changes. |  |
|  | ## Step 3
Validate your new post function
1. Remember to publish your workflow. We always recommend saving a backup
of the previous workflow when prompted.
2. Create an issue and transition the issue using one of the users specified within
your configuration to trigger your post function.
3. Validate that the transition took place and the new issue was created. | |