Copy Field Values
Use Copy Field Values to copy the values from a configured field to another on the same Jira instance. This built-in script can save you time when creating fields with the same values, eliminating the need for manual input of values.
See below for a detailed list of supported fields. If a field is not visible in your instance, then the field is not supported by this built-in script.
Notifications
When you use this built-in script to bulk update issues, users are not notified of the change according to the project notification scheme.
Create options
In some instances, a Create option checkbox becomes available for certain fields. This allows new options to be created if a matching one does not exist in the target field.
Supported fields
See the tables below for a detailed list of system and common custom fields, standard custom fields, and advanced custom fields that are supported by this built-in script. There are some things you must bear in mind when using this built-in script:
- Source and target fields must be different. Copying a field's value to itself is not permitted.
- The fields available to you will vary depending on which version of Jira you have and whether you have installed Jira Service Management. If you cannot see a field, it is likely that it is not available on your instance.
Copying values to the same field type
When you're copying values to a field of the same type, for example, from checkboxes to checkboxes, values will only be copied if the target field has the same values available. If the target field lacks any of the source field's values, existing selections in the target field may be cleared. For partial matches, only the shared values will be copied, and any non-matching values in the target field will be cleared.
Supported system fields and common Jira custom fields
| Source field | Supported target fields |
|---|---|
| Approvers |
|
| CAB |
|
| Change completion date |
|
| Change managers |
|
| Change reason | |
| Change risk | |
| Change start date |
|
| Change type | |
| Customer request type |
|
| Description |
|
| Environment |
|
| Epic color | No compatible fields |
| Epic link |
|
| Epic name | No compatible fields |
| Epic status | No compatible fields |
| Groups | No compatible fields |
| Impact | |
| Investigation reason | |
| Linked major incidents | No compatible fields |
| Operational categorization |
|
| Organizations |
|
| Original story points |
|
| Parent link | No compatible fields |
| Pending reason | |
| Product categorization |
|
| Request participants |
|
| Root cause |
|
| Source | |
| Sprint |
|
| Story points |
|
| Summary | |
| Target end |
|
| Target start |
|
| Team | No compatible fields |
| Urgency | |
| Workaround |
Supported standard custom fields
| Source field | Supported target fields |
|---|---|
Checkboxes |
|
Database picker custom field | No compatible fields |
Date picker |
|
Date time picker |
|
Labels |
|
Multiple user picker |
If a multi user picker value is copied into a single user picker then only the first value is copied. |
Multiple issue picker |
|
Multiple LDAP picker |
|
Multiple remote issue picker |
|
Number field |
|
Radio buttons |
|
Select list (cascading) |
|
Select list (multiple choices) |
For single choice select lists only the first value is copied. |
Select list (single choice) |
|
Single custom picker | No compatible field |
Single database values picker | No compatible fields |
Single issue picker |
|
Single LDAP picker | No compatible fields |
Single remote issue picker |
|
Text field (multi-line) |
|
Text field (single-line) |
|
URL field |
|
User picker (single user) |
|
Supported advanced custom fields
| Source field | Supported target fields |
|---|---|
Development summary | No compatible fields |
Global rank | No compatible fields |
Group picker (multiple groups) |
For single group pickers only the first value is copied. |
Group picker (single group) |
|
Hidden job switch | No compatible fields |
Jira released version history |
|
Job checkbox |
|
Original story points |
|
Project picker (single project) |
|
Scripted field | No compatible fields |
Text field (read only) |
|
User picker (multiple versions) |
If a multi user picker value is copied into a single user picker then only the first value is copied. |
Version picker (multiple versions) |
|
Version picker (single version) |
|
Assets object |
|
Assets object (legacy multiple) |
|
Assets object (legacy single) |
|
Assets read-only object |
|
Assets referenced object (multiple) |
|
Assets referenced object (single) |
|
Initial watchers |
|
Using this built-in script
To copy fields between supported field types:
- From ScriptRunner, navigate to Built-in Scripts > Copy field values.
Select a Filter ID. Issues returned by this filter are modified only if they contain both the source and target fields.
Only saved JQL filters show up in Filter ID. For more information on how to create and save custom filters see Saving Your Search as a Filter.
Under Source Field, select a field. Values will be copied from this field to the Target Field.
For select lists, if an option from the source field is not configured in the available target field, it is skipped. For example, the source field has options AA and BB configured, and the target field has options AA and CC configured. In this case only option AA is copied to the target field. If none of the options in the source field exist in the target and Create Options is unchecked, the target field will be cleared.
Under Target Field, select a field. All values are copied from the Source Field to this field.
If the target field already contains values, they are overwritten by any copied values.
Select Preview to see the number of issues affected by the change.
Select Run. Source fields are copied to target fields where applicable.