Skip to main content
Skip table of contents

Jira fields copy and synchronisation

Elements 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

(tick)

Any Version Picker (multiple version) field

No.

Assignee

(tick)

Any User Picker (single user) field

Yes, select any Jira user from a user picker.

Description

(tick)

Any Text Field (multi-line)
Any Text Field (single line)

Yes, set any text in a text area.

Due Date

(tick)

Any Date Picker field

Yes, select any date from a Date picker.

Environment

(tick)

Any Text Field (multi-line)
Any Text Field (single line)

Yes, set any text in a text area.

Epic Link (replaced by Parent)

(tick)

No.

Parent

(tick)

No.

Fix versions

(tick)

Any Version Picker (multiple version) field

No.

Labels

(tick)

Any Labels custom field

Yes, select any existing label on the Jira instance.

Priority

(tick)

Yes.

Reporter

(tick)

Any User Picker (single user) field

Yes, select any Jira user from a user picker.

Summary

(tick)

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

(tick)

Can be initialized with a static default value.

Affected services

(error)

Approvals

(error)

Approvers

(tick)

Can be initialized with a static default value.

Backout plan

(tick)

Can be initialized with a static or dynamic default value.

CAB

(tick)

Can be initialized with a static default value.

Change completion date

(tick)

Can be initialized with a static default value.

Change managers

(tick)

Can be initialized with a static default value.

Change reason

(tick)

Can be initialized with a static or dynamic default value.

Change risk

(tick)

Can be initialized with a static default value.

Change start date

(tick)

Can be initialized with a static default value.

Components

(tick)

Can be copied/synchronized to a different project by using an option.
Can be initialized with a static default value.

Epic Color

(error)

Epic Link

(tick)

Epic Name

(tick)

Epic Status

(error)

Flagged

(error)

Impact

(tick)

Can be initialized with a static default value.

Implementation plan

(tick)

Can be initialized with a static or dynamic default value.

Investigation reason

(tick)

Can be initialized with a static default value.

Issue color

(error)

Location

(error)

Operational categorization

(tick)

Organizations

(tick)

Original estimate

(tick)

Parent Link (replaced by Parent)

(tick)

Available in Jira Premium with Advanced Roadmaps.

Parent

(tick)

Pending reason

(tick)

Can be initialized with a static default value.

Planned end date

(tick)

Can be initialized with a static default value.

Planned start date

(tick)

Can be initialized with a static default value.

Product categorization

(tick)

Rank

(error)

Used to rank issues in Jira Boards. No need to sync.

Request language

(error)

Request participants

(error)

Coming soon.

Request Type

(tick)

Can be initialized with a static default value.

Root cause

(tick)

Can be initialized with a static or dynamic default value.

Satisfaction

(error)

Satisfaction date

(error)

Severity

(tick)

Can be initialized with a static default value.

Source

(tick)

Can be initialized with a static default value.

Sprint

(tick)

Start date

(tick)

Can be initialized with a static default value.

Status

(warning)

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

(tick)

Story Points

(tick)

Target end

(tick)

Can be initialized with a static default value.

Target start

(tick)

Can be initialized with a static default value.

Team

(tick)

Only available in Jira Premium.

Time to approve normal change

(error)

Time to close after resolution

(error)

Time to first response

(error)

Time to resolution

(error)

Time to triage normale change

(error)

Time tracking

(tick)

Can be copied, but not synchronized.

Urgency

(tick)

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

(tick)

Used by Tempo add-on.

Assets

(tick)

Used by Insight add-on.

Checkboxes

(tick)

Can be initialized with static default values.

Date of First Response

(error)

Date Picker

(tick)

Can be copied/synced to any Date Picker custom field.
Can be initialized with a static default value.

Date Time Picker

(tick)

Can be copied/synced to any Date Time Picker custom field.
Can be initialized with a static default value.

Days since last comment

(error)

Domain of Assignee

(error)

Domain of Reporter

(error)

Global Rank

(error)

Group Picker (multiple groups)

(tick)

Can be copied/synced to any Group Picker (multiple groups) custom field.

Group Picker (single group)

(tick)

Can be copied/synced to any Group Picker (single group) custom field.

Labels

(tick)

Can be copied/synced to any Labels custom field.

Last commented by a User Flag

(error)

Last public comment date

(error)

Message Custom Field (for edit)

(error)

Message Custom Field (for view)

(error)

Number Field

(tick)

Can be copied/synced to any Number custom field.
Can be initialized with a static default value.

Number of attachments

(error)

Number of comments

(error)

Parent Link

(tick)

Available in Jira Premium with Advanced Roadmaps.

Participants of an issue

(error)

Project Picker (single project)

(tick)

Radio Buttons

(tick)

Can be initialized with static default values.

Select List (cascading)

(tick)

Select List (multiple choices)

(tick)

Can be initialized with static default values.
Options from any context can be used.

Select List (single choice)

(tick)

Can be initialized with a static default value.
Options from any context can be used.

Team

(tick)

Only available in Jira Premium.

Team

(tick)

Used by Tempo add-on.

Text Field (multi-line) / Paragraph

(tick)

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

(error)

Text Field (single line)

(tick)

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

(error)

URL Field

(tick)

User Picker (multiple users)

(tick)

Can be copied/synced to any User picker (multiple users) custom field.
Can be initialized with a static default value.

User Picker (single user)

(tick)

Can be copied/synced to any User picker (single user) custom field.
Can be initialized with a static default value.

User Property Field

(error)

Username of last updater or commenter

(error)

Version Picker (multiple versions)

(tick)

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)

(tick)

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

(tick)

Security Level

(tick)

Available from Jira Standard and up. See official documentation.

Jira Forms

(tick)

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

(tick)

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.

JavaScript errors detected

Please note, these errors can depend on your browser setup.

If this problem persists, please contact our support.