Create issue

Created by Marcin Żurawiecki
Nov 03, 2020

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

  1. Select if the created issue should be a sub-task of or linked to the source issue in the Relation type field

    1. If None was selected, set the details of the issue that will be created:

      1. Set the project where the new issue will be created in the Project field

      2. Set the issue type of the issue in the Issue type field

    2. If Sub-task was selected, choose the issue type of the new issue in the Issue type field

    3. If Linked was selected, set the details of the issue that will be created and the issue link connecting both issues:

      1. Set the project where the new issue will be created in the Project field

      2. Set the issue type of the issue in the Issue type field

      3. Set the type of link in the Link type field

      4. Set the direction of link in the Link direction field

  2. 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)

  3. 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)

  4. Set the assignee of the issue in the Assignee field

  5. 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)

  6. Select if the post function should be executed by the current or another user in the Action executor field (see User Permissions below)

    1. If you have selected Current user option, the post function will be executed by the user making the workflow transition

    2. 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

  7. 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”)

  8. 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

    1. Select if The executor has to be or can’t be a member of a certain Jira user group or project role

      1. Select a Jira user group in the Group field if Group was set in the member of a field

      2. 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:

  • {source.summary} - summary field value

  • {source.status} - status field value

  • {source.project} - project name

  • {source.key} - issue key

  • {source.resolution} - resolution field value

  • {source.priority} - priority field value

  • {source.assignee.email} - e-mail address of the user assigned

  • {source.assignee.username} - username of the user assigned

  • {source.assignee.displayName} - full name of the user assigned

  • {source.reporter.email} - e-mail address of the reporter

  • {source.reporter.username} - username of the reporter

  • {source.reporter.displayName} - full name of the reporter

  • {source.projectlead.email} - e-mail address of the project lead

  • {source.projectlead.username} - username of the project lead

  • {source.projectlead.displayName} - full name of the project lead

  • {source.watchers.email} - e-mail addresses of all watchers

  • {source.watchers.username} - usernames of all watchers

  • {source.watchers.displayName} - full names of all watchers

  • {source.singleuser.customfield_id.email} - e-mail address of the user set in a single user picker custom field defined by id

  • {source.singleuser.customfield_id.username} - username of the user set in a single user picker custom field defined by id

  • {source.singleuser.customfield_id.displayName} - full name of the user set in a single user picker custom field defined by id

  • {source.multiusers.customfield_id.email} - e-mail addresses of all users set in a multi user picker custom field defined by id

  • {source.multiusers.customfield_id.username} - usernames of all users set in a multi user picker custom field defined by id

  • {source.multiusers.customfield_id.displayName} - full names of all users set in a multi user picker custom field defined by id

  • {source.text.customfield_id} - value of a text custom field defined by id

  • {source.number.customfield_id} - value of a number custom field defined by id

  • {source.date.customfield_id} - value of a date custom field defined by id

  • {source.singleselect.customfield_id} - value of a single select custom field defined by id

  • {source.multiselect.customfield_id} - value of a multi select custom field defined by id

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