Additional time may be available from the app vendor.
About Data Center trials
OVERALL RATINGS
INSTALLS
61
SUPPORT
- Partner Supported
- Cloud Migration Assistance
Key highlights of the appCopy field values between Jira issues automatically
Field Synchronization
Define listeners to copy values between parent & subtasks, linked issues, epics & stories, Jira Portfolio parent&children
Multiple Listeners
Define multiple listeners for different sync needs across your system
Advanced Configuration
Each listener can be configured to work with a different set of projects, issuetypes, link types, events, sync direction
Supporting media
More details
Field Sync apps gives you the ability to copy field values between jira issues automatically.
The app listens to updates on Jira issues and copies changed field values between parent & subtasks, linked issues, epic & stories and Jira Portfolio parent & child issues.
The app can sync both system and custom fields.
Advanced configuration options allow you to define detailed JQL's to select source and target issues, events, link directions and fields to copy.
The new version 5 supports transitive syncs in which one update made by a listener can trigger a sync in another listener. This structure can lead to a chain of syncs across many issues.
Resources
Download
Get the .jar file downloaded to your system
App documentation
Comprehensive set of documentation from the partner on how this app works
Privacy and Security
Privacy policy
Atlassian's privacy policy is not applicable to the use of this app. Please refer to the privacy policy provided by this app's partner.
Partner privacy policySecurity program
This app is part of the Marketplace Bug Bounty program.
About Bug Bounty programVersion information
Version 5.12.0.3•for Jira Data Center 8.0.0 - 11.3.12
- Release date
- Sep 23rd 2026
- Summary
- Security Hardening
- Details
Summary
- Security Hardening
Behaviour changes
Field Sync now checks Jira permissions before every write. A synchronization runs as the listener's service user when one is configured, otherwise as the user who made the change.
- Target issues are only updated when that user has Edit Issues on them.
- Security Level is only synchronized with Set Issue Security on the target; Assignee only with Assign Issues, and only if the assignee is assignable in the target project.
- Comments are only copied with Add Comments on the target. Restricted comments keep their visibility and are not copied if the restriction cannot be applied there.
- Watchers follow Jira's own rules: users may add themselves, but a watcher who cannot browse the target is not copied.
- Source and parent issues the user cannot browse are no longer read.
- Changes propagated by Field Sync are passed on as updates, so listeners with Sync on create disabled may now act on later links in a chain.
- A listener whose service user cannot be found is skipped instead of running as the triggering user.
- Changes made by anonymous or system actors (mail handlers, anonymous issue creation, post-functions without a user) are not synchronized unless a service user is configured.
Action required: if a listener must keep working for users without these permissions, or for mail handlers and automation, configure a dedicated service user with the required permissions. Recently skipped synchronizations and their reasons are shown on the Listener List page.
- Payment model
- Paid via Atlassian