Field Sync - Copy Fields to Child & Linked Issues for Jira

Server/DC and Cloud Feature Comparison

Core features of Server/DC and Cloud versions of Field Sync are identical, but some features differ between the two platforms.

Below you can find the feature compatibility table.

We'll be updating this table as new features are introduced.

Some sub-features will be added to this table as a row when there is a disparity between Cloud and Server/DC about that sub-feature. That row might be removed when the parity is achieved and they will be represented by just the parent feature row in the table. In other words, if you can't find a row in the table that you saw earlier (which showed a feature disparity between Cloud and Server/DC), that is probably because that feature is implemented in both platforms so that feature disparity no longer exists.


Item

Server / DC 

Cloud

Notes

Listener Types

Sub-task sync

check mark

check mark


Epic-Story sync

check mark

check mark

DC: sub-task, Epic-Story and Plans/Advanced Roadmaps hierarchies each have their own listener.

Cloud: Jira Cloud doesn’t separate these hierarchies, so Cloud combines them into a single Parent-Child Listener.

Advanced Roadmaps parent-child sync

check mark

check mark


Linked issue sync

check mark

check mark


Multiple listeners per type

check mark

check mark


Scope

Sync across all projects

check mark

check mark


Issue type filter

check mark

check mark


Separate source and target issue types

check mark

check mark


Target Issue JQL

check mark

check mark


Source issue JQL

check mark

check mark


Issue link type filter

check mark

check mark


Fields

System and custom fields

check mark

check mark


Append values to target fields

check mark

check mark


Sync Behavior

Bidirectional sync

check mark

check mark


Single-direction sync

check mark

check mark


Loop protection

check mark

check mark


Sync Identity

Run as the user who made the change

check mark

check mark


Run as a service user

check mark

check mark


Run as the Field Sync App

cross mark

check mark


Triggers

Sync on Link

check mark

check mark


Sync on Move

check mark

check mark


Sync On Create

check mark

cross mark

DC: Available as a separate trigger.
Cloud: Covered by Sync on Link. Jira Cloud always sends a link event when an issue is created with a parent or a link, so values are synced at creation time.

Suppress Notifications

check mark

check mark

DC: Always on and can’t be turned off. No admin permission is needed.
Cloud: Optional setting. The sync must run as a Jira administrator or as the Field Sync app.

Allow sync on not editable issues

check mark

cross mark


Administration

Download app logs

check mark

check mark


Sync restricted issues

check mark

check mark

Cloud: in team-managed projects, the Field Sync app user must be added to the relevant project roles with the Jira REST API. In company-managed projects, this can be done from the Jira UI.

Sync existing issues (bulk sync by JQL)

check mark

cross mark