Sync Bridge for Jira Cloud
Sync Bridge for Jira Cloud
Breadcrumbs

Sync Two Internal Jira Sites

📘 What you will learn here

On this page you will learn how to sync two Jira Cloud sites in your organization, for example a support site and a development site, so you can hand work items from one team to the other and keep both sides up to date.

The scenario

  • Sync Bridge is installed on the support site (This Jira site).

  • Support agents escalate selected work items, for example bugs, to a space on the development site. Sync Bridge creates the linked work item there.

  • Developers work in their own site. Their progress, and optionally their comments, come back to the support work item.

Install Sync Bridge on the site where work items start. Linked work items are only created by pushing from this Jira site. Pull updates work items that are already linked, but doesn't create new ones.

1. Connect to the other site

On the Connectors page, create a connector with the Site URL of the development site and the Email and API token of an account there. Use a dedicated account for the sync, with permission to create, edit, comment on and transition work items in the target space. Everything Sync Bridge writes on the development site is done as that account.

2. Choose a direction

Option

Settings

Use it when

Hand over only

Push only. Map fields, comments and attachments as Source → Target.

The development team needs a copy of the work item, and support doesn't need updates back.

Hand over and track progress

Both directions. Map fields as Source → Target, and status transitions as Target → Source.

Support should see when development starts or finishes, without developers changing support data.

Full collaboration

Both directions. Set comments, attachments and the fields both teams edit to Both directions.

Both teams discuss and update the same work.

Anything that should come back from the development site needs Pull turned on with the Scheduler trigger. With Push only, nothing comes back.

Setting

Recommendation

Notes

Source scope

Only the work items to escalate, for example the support space and the Bug work type, or an Advanced JQL query such as a label.

Work items outside the scope never sync.

Choosing work items

Either narrow the scope as above, or turn on the Per-work-item sync switch with Off by default and let agents switch on the work items to escalate.

See Turn Sync On or Off for a Work Item.

Push triggers

Jira events with Work item created and the other events you need. Keep Manual on.

If you only want status changes to go across, select Status changed without Work item updated, so other edits don't start a field sync.

Escalation from automation

Turn on the API trigger and call it from a Jira automation rule.

For example, escalate when an agent moves a work item to an Escalated status. See Sync Trigger API.

Pull schedule

Scheduler with a schedule that matches how quickly support needs updates.

Only needed for Both directions.

Comments

If the support space is a Jira Service Management space, add the Visibility filter.

Choose Public comments only, Internal comments only or Public and internal comments. Internal comments that sync become regular comments on the other site. See Comments Sync.

4. Keep an eye on it