Create issue
Overview
The Create issue post function allows you to create an issue when a workflow transition is executed. You can define the project, issue type and the relation (sub-task or linked) to the issue triggering the post function. The Summary and Description fields can be set directly. You can use macros to add dynamic data to the fields. Also, other fields may be copied from the source issue.
Configuration
Select if the created issue should be a sub-task of or linked to the source issue in the Relation type field
If None was selected, set the details of the issue that will be created:
Set the project where the new issue will be created in the Project field
Set the issue type of the issue in the Issue type field
If Sub-task was selected, choose the issue type of the new issue in the Issue type field
If Linked was selected, set the details of the issue that will be created and the issue link connecting both issues:
Set the project where the new issue will be created in the Project field
Set the issue type of the issue in the Issue type field
Set the type of link in the Link type field
Set the direction of link in the Link direction field
Provide the summary of the issue in the Summary field (e.g. “This is a summary of an automatically created issue”). You can use macros to add dynamic data (see the Macros section below)
Provide the description of the issue in the Description field (e.g. “This is a description of an automatically created issue”). You can use macros to add dynamic data (see the Macros section below)
Set the assignee of the issue in the Assignee field
Select the fields to be copied from the issue triggering the post function to the new issue in the Fields to copy field (see Supported fields below)
Select if the post function should be executed by the current or another user in the Action executor field (see User Permissions below)
If you have selected Current user option, the post function will be executed by the user making the workflow transition
If you have selected Another user option, provide a user in the User field, so that the post function will be executed by this user
Activate the JQL condition option and define the JQL query that has to be met by the issue in order to execute the post function (e.g. “type = Bug and Priority = Blocker”)
Activate the Executor condition option if you want the post function to be executed only if the user is or isn’t in a certain Jira user group or project role
Select if The executor has to be or can’t be a member of a certain Jira user group or project role
Select a Jira user group in the Group field if Group was set in the member of a field
Select a project role in the Project role field if Project role was set in the member of a field
User Permissions
The user set as Action executor in point 6 needs to have the Create issues permission in the project where the issue will be created in order to execute the post function.
Supported fields
The Fields to copy field in the post function supports all custom fields available in Jira by default. Fields provided by external apps are not supported.
Macros
Macros can be used to add dynamic data related to the issue or the project to the comment text. Following macros are available:
Use cases
Create multiple onboarding sub-tasks, when the parent onboarding issue is approved
Create a bug issue automatically when the Story issue is transitioned back to Development through the Failed transition