Breadcrumbs

Copy field values from multiple issues

This post function allows you to copy field values from one or multiple issues which are returned by an issue list or a JQL query.

Field values can also be aggregated or calculated. Make sure to familiarize yourself with the JQL mode and the Issue list mode which are used to define the target list of issues to copy values from.


⚒️ Configuration

Target field

Select the target fields that will be set and the source values for each of them. The following options are available:

Option

Description

Copy field from selected issues

The value(s) found in the issues specified in the next parameter "Issues to copy from" will be copied to the target field as a comma separated list.

Since you are copying the values of potentially multiple issues returned by a JQL query or an issue list JWT can aggregate values, and offers additional options depending on the type of source field.

Calculated values

For date and date-time fields you can additionally choose to only return the:

  • Earliest date value among those being returned.

  • Latest date value among those being returned.

For numeric fields you can automatically return the following aggregated values:

  • Sum of values: sum of all the values being returned.

  • Lowest value: minimum value among those being returned.

  • Highest value: maximum value among those being returned.

  • Average value: arithmetic mean of values being returned.

When updating the Priority field you can additionally choose to only return the:

  • Highest priority value among those being returned.

  • Lowest priority value among those being returned.

Set field value manually (parser expression)

Set the value of the target field using an expression and optionally use field codes. The Parsing modes differ depending on the data type of the target field. 

You can either choose from the Advanced text mode or the Numeric mode.

Clear field value

Choose this option to clear the value of the target

field. This option is not available for the Summary field.

Check the write protection option if you want to prevent a field to be updated, if it already has a value. If checked, only empty fields will be set.

Issues to copy from

Enter a JQL query or an issue list and optionally use field codes to define the target list of issues the values will be copied from.

Make sure to familiarize yourself with the JQL mode and the Issue list mode

Additional options

Choose to update issues immediately if you want Jira to fire a separate "Issue updated" event for any field change.  This will also result in a dedicated issue history entry.

Condition execution

You can optionally specify a logical expression to define the circumstances (or conditions) under which the post function should be executed.

The result of the logical expression must return a boolean value of either:

  • true → the post function will be executed

  • false → the post function will not be executed

Using the conditional operator, even complex or multi-layered conditions can be constructed.

Make sure to learn more about defining logical expressions and browse through the various examples here: Logical mode

Run as

Select which user will be used to execute this post function. By default this parameter is set to the current user. You can also use field codes to run the function as a dynamic user (e.g. current assignee).

Make sure that the user running the post function has all the relevant permissions to perform the actions defined in the configuration (e.g. "Update Issues")!

If you want to keep track the actions being performed automatically, we suggest to create a dedicated JWT account, granted all relevant permissions, and use it in the Run as parameter to identify which changes have been made with JWT.


📚 Use cases and examples

Use case
No content found.