Skip to main content
Version: Next

Cross-Site Sync for Jira

Cross-Site Sync for Jira syncs work items between two Jira Cloud sites. Install the app on one site only: the local site. The remote site does not install the app; an administrator connects it through a technical account and an API token.

What you can do​

  • Check setup progress, connection health, and items that need attention from the administration overview.
  • Create connections and test remote site access, spaces, work types, and attachment permissions.
  • Create rules with a six-step wizard that autosaves drafts and lets you revisit earlier steps without losing your entries.
  • Search local and remote spaces and work types, preview field mappings, and simulate a rule before activating it.
  • Create a remote work item from a workflow transition, a field value, or the panel. Each local work item creates at most one remote work item per rule.
  • Check the site's plan and connection limit, and sync changes from the remote site from the panel when needed.
  • Sync comments and attachments according to the configured policies. Attachments cited in comments are copied to the destination and the comment links to the copy.
  • Review and resolve links, adjust activity log retention, and configure token expiry notices sent by email and shown in Summary.
  • Configure the Cross-Site Sync validator and post function on a workflow transition.

Local and remote sites​

Install the app on the local site. An administrator connects the remote site with a technical account that can create work items in the destination. The remote site does not need the app.

When the remote work item is created, Jira adds a native remote link to both work items. Sync also sends the fields, comments, and attachments allowed by the rule. The app therefore needs outbound access to Jira Cloud sites and is not Runs on Atlassian.

Plans and sync frequency​

The plan uses the highest user count among Jira Software, Jira Core, Jira Service Management (JSM), and Jira Work Management. Product user counts are not added together, so people with access to multiple products are not counted more than once. The interface shows the generic total Jira has {users} users, without a product breakdown.

UsersPlanConnectionsAutomatic sync from the remote site
Up to 10Free1Every hour
More than 10PaidNo artificial limitEvery 5 minutes

On both plans, outgoing comments and attachments are sent immediately according to the rule, and Sync now lets you retrieve remote changes without waiting for the next cycle.

Upgrade from version 1.1.0​

Upgrade directly to version 1.2.0 without reconfiguring existing connections or rules. This release adds the free plan for sites with up to 10 users, manual sync from the panel, and a clearer empty state.

Existing connections are kept if the site moves to the free plan; the free limit applies to new connections and reactivations. Automatic sync becomes hourly.

Remaining limitations​

  • Jira Data Center or Confluence.
  • OAuth 2.0 (3LO).
  • Creating work items from the remote site to the local site.
  • Syncing fields after the remote work item is created or mapping statuses to local transitions.
  • Editing or deleting comments and attachments that have already synced.
  • Completing an unlink-and-relink flow from the panel: the interface does not provide an Unlink action, and pausing does not remove the link.
  • Displaying transferred images inline in the destination comment; files are attached to the destination work item.
  • Historical metrics dashboard, activity log export, Marketplace listing, or license management.

Start with the installation guide, the administrator guide, or the user guide.