Jira fields copy and synchronisation

Copy the status of an issue to a cloned issueElements Copy & Sync lets you copy and synchronize fields between Jira issues. This can be done with native Jira fields, and custom fields as well.

In this page, you will find the list of fields supported by our add-on, as well as the list of other add-ons it integrates with.

Basic Jira fields

Field name	Supported	Can be copied or synchronized to	Can be initialized with a static default value
Affects versions		Any Version Picker (multiple version) field	No.
Assignee		Any User Picker (single user) field	Yes, select any Jira user from a user picker.
Description		Any Text Field (multi-line) Any Text Field (single line)	Yes, set any text in a text area.
Due Date		Any Date Picker field	Yes, select any date from a Date picker.
Environment		Any Text Field (multi-line) Any Text Field (single line)	Yes, set any text in a text area.
Epic Link (replaced by Parent)			No.
Parent			No.
Fix versions		Any Version Picker (multiple version) field	No.
Labels		Any Labels custom field	Yes, select any existing label on the Jira instance.
Priority			Yes.
Reporter		Any User Picker (single user) field	Yes, select any Jira user from a user picker.
Summary		Any Text Field (multi-line) Any Text Field (single line)	Yes, set any text in a text field.

Custom fields

System fields

Built-in fields can only be copied and synchronized with themselves or to other fields of the same type. 

Custom Field	Supported	Comment
Affected hardware		Can be initialized with a static default value.
Affected services
Approvals
Approvers		Can be initialized with a static default value.
Backout plan		Can be initialized with a static or dynamic default value.
CAB		Can be initialized with a static default value.
Change completion date		Can be initialized with a static default value.
Change managers		Can be initialized with a static default value.
Change reason		Can be initialized with a static or dynamic default value.
Change risk		Can be initialized with a static default value.
Change start date		Can be initialized with a static default value.
Components		Can be copied/synchronized to a different project by using an option. Can be initialized with a static default value.
Epic Color
Epic Link
Epic Name
Epic Status
Flagged
Impact		Can be initialized with a static default value.
Implementation plan		Can be initialized with a static or dynamic default value.
Investigation reason		Can be initialized with a static default value.
Issue color
Location
Operational categorization
Organizations
Original estimate
Parent Link (replaced by Parent)		Available in Jira Premium with Advanced Roadmaps.
Parent
Pending reason		Can be initialized with a static default value.
Planned end date		Can be initialized with a static default value.
Planned start date		Can be initialized with a static default value.
Product categorization
Rank		Used to rank issues in Jira Boards. No need to sync.
Request language
Request participants		Coming soon.
Request Type		Can be initialized with a static default value.
Root cause		Can be initialized with a static or dynamic default value.
Satisfaction
Satisfaction date
Severity		Can be initialized with a static default value.
Source		Can be initialized with a static default value.
Sprint
Start date		Can be initialized with a static default value.
Status		Its name can be copied to any text field. Follow this tutorial to copy an issue status: Copy the status of an issue to a cloned issue
Story point estimate
Story Points
Target end		Can be initialized with a static default value.
Target start		Can be initialized with a static default value.
Team		Only available in Jira Premium.
Time to approve normal change
Time to close after resolution
Time to first response
Time to resolution
Time to triage normale change
Time tracking		Can be copied, but not synchronized.
Urgency		Can be initialized with a static default value.

Custom fields types

Jira admins can create new Custom Fields at all times on any Jira instance. Once a new field has been created, it becomes available in the recipe configuration and can be added to the fields mapping depending on their fields types to be copied and synchronized with fields with similar types. The table below lists the compatible Custom Field types which can be copied and synchronized.

Custom Field type	Supported	Comment
Account		Used by Tempo add-on.
Assets		Used by Insight add-on.
Checkboxes		Can be initialized with static default values.
Date of First Response
Date Picker		Can be copied/synced to any Date Picker custom field. Can be initialized with a static default value.
Date Time Picker		Can be copied/synced to any Date Time Picker custom field. Can be initialized with a static default value.
Days since last comment
Domain of Assignee
Domain of Reporter
Global Rank
Group Picker (multiple groups)		Can be copied/synced to any Group Picker (multiple groups) custom field.
Group Picker (single group)		Can be copied/synced to any Group Picker (single group) custom field.
Labels		Can be copied/synced to any Labels custom field.
Last commented by a User Flag
Last public comment date
Message Custom Field (for edit)
Message Custom Field (for view)
Number Field		Can be copied/synced to any Number custom field. Can be initialized with a static default value.
Number of attachments
Number of comments
Parent Link		Available in Jira Premium with Advanced Roadmaps.
Participants of an issue
Project Picker (single project)
Radio Buttons		Can be initialized with static default values.
Select List (cascading)
Select List (multiple choices)		Can be initialized with static default values. Options from any context can be used.
Select List (single choice)		Can be initialized with a static default value. Options from any context can be used.
Team		Only available in Jira Premium.
Team		Used by Tempo add-on.
Text Field (multi-line) / Paragraph		Can be copied/synced to any Text Field (multi-line) custom field. Can be initialized with a static or dynamic default value.
Text Field (read-only) / Short text
Text Field (single line)		Can be copied/synced to any Text Field (single line) custom field. Can be initialized with a static or dynamic default value.
Time in Status
URL Field
User Picker (multiple users)		Can be copied/synced to any User picker (multiple users) custom field. Can be initialized with a static default value.
User Picker (single user)		Can be copied/synced to any User picker (single user) custom field. Can be initialized with a static default value.
User Property Field
Username of last updater or commenter
Version Picker (multiple versions)		Can be copied/synced to any Version picker (multiple version) custom field. Versions can be copied/synchronized to a different project by using an option.
Version Picker (single version)		Can be copied/synced to any Version picker (single version) custom field. Versions can be copied/synchronized to a different project by using an option.

Other data and add-ons

Elements Copy & Sync can also be used to copy and synchronize data that is not stored in fields.

Type of Data	Supported	Comment
Issue Resolution
Security Level		Available from Jira Standard and up. See official documentation.
Jira Forms		Use the "Jira Forms" option in the Fields Mapping table of a recipe to copy and synchronize forms between any issues. Learn more about Jira Forms (formerly ProForma).
Issue Checklist for Jira		Use the "Issue Checklist for Jira" option in the Fields Mapping table to copy and synchronize checklists between any issues. You can follow our step-by-step guide to help you in your configuration.