Copy field value to related issues

Overview

The Copy field value to related issues post function allows you to copy the value of a custom field to another custom field on sub-task, parent, or linked issues when a workflow transition is executed.

Configuration

  1. Select the relation type in the Perform action on field to decide if the custom field value will be copied to another field on sub-task, parent, or linked issues

    1. If Parent or Sub-tasks was selected, set the Applies to field to decide if the custom field value will be copied to another field on issues with any or selected issue type. If Selected was set, choose the issue types in case of which the custom field value will be copied in the Issue types field

    2. If Linked was selected, set the Applies to field to decide if the custom field value will be copied to another field on issues linked with any or selected issue link. If Selected was set, define the details of the issue link used to link issues to which the custom field value will be copied:

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

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

  2. Select a custom field whose value will be copied in the Source custom field field (see Supported fields below)

  3. Select a custom field to which the value will be copied in the Target custom field field (see Supported fields below)

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

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

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

  7. Activate the Fire event option if you want Jira to fire the ISSUE_UPDATED event

  8. Activate the Send notification option if you want Jira to send the notification according to the configured notification scheme. The option requires the Fire event option to be enabled in order to send the notification

User Permissions

The user set as Action executor in point 4 needs to have the Browse Projects and Edit Issues permissions in the project of the related issue in order to execute the post function.

Field compatibility

Source and target fields should be of the same type. Mixing different types of custom fields is not supported and may not work.

Supported fields

The post function supports all custom fields available in Jira by default. Fields provided by external apps are not supported.

The following custom fields are compared by the option name (e.g. “First option”):

  • Select List (single choice)

  • Select List (multiple choices)

  • Checkboxes

In case of these custom fields, if the Target custom field doesn’t contain the option to be copied from the Source custom field, the value will not be copied.

Use cases

  • Copy the release date to the sub-task issues if the parent issue gets the approval