Sync Bridge for Jira Cloud
Keep work items in sync between Jira Cloud sites, so your teams, partners and customers all see the latest updates.
🧩 What does the app do?
Your teams, partners and customers each work in their own Jira. Sync Bridge keeps work items in sync between Jira Cloud sites, so everyone sees the latest updates without leaving the tool they know. It's built on Atlassian Forge.
You install Sync Bridge on your own Jira Cloud site, and that's it. The other site only needs a user account with an API token: no app to install and no admin approval to chase on their side. Sync Bridge sends your changes out as they happen, and checks the other site on a schedule you set to bring their changes back.
-
New here? Start with Getting Started to set up your first sync in a few steps.
✨ Key features
-
🏠 Install on one site only
The other site doesn't need Sync Bridge. A connector with a user account and API token is enough. -
🔄 Sync fields, status, comments and attachments
Choose Push only, Pull only or Both directions for each sync rule. -
⚡ Real-time push, scheduled pull
Changes on your site are pushed as they happen. Changes on the other site are pulled on your own schedule, every 5 minutes by default. -
🧭 Flexible mapping
Map fields, statuses, spaces and work types, and transform values with smart values. -
🔒 Keep private content private
Filters keep internal comments and attachments on your side. -
🧱 No-code sync rules
Set up sync rules without code, and reuse one connector across many rules.
🔧 Control and monitoring
-
📊 Track all sync activity on the dashboard.
-
📜 See sync status and full sync history on every work item.
-
⏸️ Pause or resume sync for a single work item.
-
🔎 Find synced and failed work items with JQL.
-
🔌 Trigger syncs from external tools through a token-secured REST API.
-
📦 Export and import sync rules to reuse setups across sites.
🔌 Supported systems
-
Jira Cloud ↔ Jira Cloud
More systems are on the way. Need a specific one? Contact us and tell us what you use.
🚀 Quick links
🏷️ Current version: 1.0.0
Release Notes
⚙️ How it works
-
Install Sync Bridge on your Jira Cloud site, called This Jira site in the app.
-
Connect the other Jira Cloud site with a connector: its address, a user account and an API token.
-
Create a sync rule: which work items to sync, in which direction, and how fields and statuses map.
-
Work as usual. Sync Bridge pushes your changes right away and pulls changes from the other site on schedule. Every sync is recorded in Sync history.
Push creates the linked work item on the other site. Pull updates work items that are already linked; it doesn't create new ones on This Jira site.
🧭 Next steps
-
Installation Guide: install Sync Bridge and check the required permissions.
-
Getting Started: create a connector and a sync rule, and sync your first work item.
-
Administrator Guide: all connector and sync rule settings in detail.
📚 Documentation
Installation Guide
Getting Started
Administrator Guide
User Guide
API Guide
Use Cases
Troubleshooting
Current Limitations
Release Notes
FAQ and Support
-
Do I need to install Sync Bridge on both Jira sites? -
Can I sync with a Jira site I don't own, such as a customer's? -
Where is my data stored? -
Does Sync Bridge sync my existing work items when I create a sync rule? -
How fast does a change sync? -
Do changes on the other site come back to This Jira site? -
Can syncing in both directions end up in a loop? -
What happens when I delete something? -
Who appears as the author of synced work items and comments? -
Who can configure Sync Bridge, and who can use it on work items? -
How do I find all work items with a failed sync? -
Why can't I change a sync rule's connectors or scope? -
What happens when my trial or license ends? -
How long is sync history kept?