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 |
|
|
|
|
Epic-Story sync |
|
|
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 |
|
|
|
|
|
Linked issue sync |
|
|
|
|
|
Multiple listeners per type |
|
|
|
|
|
Scope |
Sync across all projects |
|
|
|
|
Issue type filter |
|
|
|
|
|
Separate source and target issue types |
|
|
|
|
|
Target Issue JQL |
|
|
|
|
|
Source issue JQL |
|
|
|
|
|
Issue link type filter |
|
|
|
|
|
Fields |
System and custom fields |
|
|
|
|
Append values to target fields |
|
|
|
|
|
Sync Behavior |
Bidirectional sync |
|
|
|
|
Single-direction sync |
|
|
|
|
|
Loop protection |
|
|
|
|
|
Sync Identity |
Run as the user who made the change |
|
|
|
|
Run as a service user |
|
|
|
|
|
Run as the Field Sync App |
|
|
|
|
|
Triggers |
Sync on Link |
|
|
|
|
Sync on Move |
|
|
|
|
|
Sync On Create |
|
|
DC: Available as a separate trigger.
|
|
|
Suppress Notifications |
|
|
DC: Always on and can’t be turned off. No admin permission is needed.
|
|
|
Allow sync on not editable issues |
|
|
|
|
|
Administration |
Download app logs |
|
|
|
|
Sync restricted issues |
|
|
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) |
|
|
|