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

Overview

Overview

Field Sync App logo


Field Sync for Jira is a Jira Cloud app that synchronizes field values between related Jira issues. Each listener watches Jira issue events and copies the selected field values from the source issue to its target issues, based on the rules you define.

Field Sync works on two kinds of relationships: parent-child hierarchies (Sub-tasks, Epics to Stories, and Jira Plans (formerly Advanced Roadmaps) parent-child levels) and standard Jira issue links (such as Blocks, Relates to, or Clones).

Installing & Accessing Field Sync

Field Sync for Jira can be installed from the Atlassian Marketplace.

Search for “Field Sync” in the Marketplace, open the app listing, and click “Try it free”. Select the Jira site where you want to install the app, review the details, and click “Start Free Trial”. Atlassian will then install the app and give you a 30-day evaluation license.

After installation, Field Sync settings can be accessed from Jira admin settings > Apps, by selecting Field Sync under Marketplace apps in the left sidebar.

Learn more: Installing Field Sync

Listeners

Field Sync is configured through listeners. Each listener listens to Jira issue events, such as issue updates or issue linking, and synchronizes selected field values to target issues.

  • Source issue: the issue on which the field update or Jira event occurs.

  • Target issue(s): the issue or issues selected by the listener to receive the synchronized field values.

Listeners can be created, edited, activated, deactivated, and deleted from the Field Sync settings page. You can create multiple listeners of each type, each with its own configuration.

Learn more: Configuration

Listener Types

Field Sync provides two listener types:

  • Parent-Child Listener: synchronizes field values between parent and child issues across Jira Cloud hierarchies, including Sub-task, Epic-Story, and multi-level Jira Plans (formerly Advanced Roadmaps) parent-child relationships.

  • Linked Issue Listener: synchronizes field values between Jira issues connected through standard Jira issue links, such as Blocks, Relates to, and Clones.

Learn more: Parent-Child Listener Configuration, Linked Issue Listener Configuration

Fields and Sync Behavior

Each listener lets you select the fields to be synchronized between source and target issues. Both system and custom fields are supported.

The Append option determines how source field values are applied to target issues. When selected, source values are added to the existing values in the target issue. When not selected, target values are replaced with the source values.

Scope and Sync Direction

Each listener can be limited to specific issues using the following settings:

  • Projects: run the listener across all projects or only in selected projects

  • Source and Target Issue Types: limit which issue types can trigger a sync and which can receive synced values

  • Source and Target Issue JQL (Optional): filter source and target issues with any valid JQL query

  • Issue Link Type: for Linked Issue Listeners, choose which link types the listener follows to find target issues

Sync direction can be set to both directions or a single direction: Parent to Child or Child to Parent for Parent-Child Listeners, and Outward or Inward for Linked Issue Listeners.

Sync Mechanics and Triggers

The Run Sync As setting defines the identity Field Sync uses to update target issues: the Original Update User, a selected Service User, or the Field Sync App. The Service User and Field Sync App options allow synchronization even when the user who updates the source issue does not have permission to edit the target issue.

Additional triggers are available for each listener:

  • Sync on Move: syncs field values when issues are moved

  • Sync on Link: syncs field values when issues are linked, or when a child issue is assigned to a parent or its parent is changed

  • Suppress Notifications: prevents notification emails from being sent to users watching the updated target issues

Learn more: Parent-Child Listener Configuration, Linked Issue Listener Configuration

Performance and Loop Protection

Updates made by Field Sync on target issues also cause update events, which can trigger further levels of sync. Field Sync has a built-in loop avoidance check and does not update the same issue twice based on a single user action. It also stops updating target issues when it reaches a maximum of 50 levels or 1,000 issues. These are built-in checks and do not require any configuration.

To avoid unnecessary load on the server, it is best practice to define projects and issue types for each listener, define a Source Issue JQL only when needed, and deactivate listeners that are no longer used.

Learn more: Performance Optimization