📘 What you will learn here
On this page you will learn what Sync Bridge 1.0.0 doesn't do and which fixed limits apply to supported systems, fields, comments, attachments, status and the product.
Read it before you plan a sync so you know what to expect.
Supported systems
-
This release supports Jira Cloud ↔ Jira Cloud only. Other ticketing systems, and Jira Server or Data Center, are not supported in this release.
-
Sync Bridge is installed on one Jira Cloud site (This Jira site). The source of every sync rule is This Jira site; the other site is always the target.
-
The other site must be reached at its Atlassian Cloud address (
https://your-site.atlassian.net). Sync Bridge can only connect to*.atlassian.netand*.atlassian.comaddresses. -
Connectors use an email address and API token. Other sign-in methods, such as OAuth, aren't supported.
What syncs, and when
|
Limit |
Details |
|---|---|
|
No bulk sync of existing work items |
Creating a sync rule doesn't sync existing work items. A work item syncs the first time one of the rule's triggers fires for it: a selected Jira event, a manual push, or an API call. |
|
Pull doesn't create work items |
Pull only updates work items on This Jira site that are already linked. New work items on the other site aren't brought over. |
|
Pull interval |
Scheduled pull checks for changes at most every 5 minutes (the default). A cron expression that runs more often is treated as every 5 minutes. Schedule times are in UTC. |
|
Pull starts from the time it is turned on |
The first scheduled check starts from the current time. Changes made on the other site before that aren't pulled. |
|
Work items per pull check |
Each scheduled check pulls up to 250 changed work items per sync rule. Any remaining work items are picked up in the following checks. |
|
Loop protection |
If a work item is pulled more than 12 times within one hour, pull pauses for that work item and the panel shows Sync failed with Pull paused: this work item changed more than 12 times in a short period. Pull resumes automatically when the hour is over. |
|
No automatic retry |
A failed sync isn't retried automatically. Use Retry in the panel or Retry sync in Sync history, or wait for the next trigger. |
|
One target space per rule |
Each sync rule creates work items in one target space. Use several rules to sync to several spaces. |
|
Deleted work items |
Deleting a work item on This Jira site doesn't delete its linked work item on the other site. If the linked work item is deleted, the panel shows that it's unreachable; select Unlink so the next push creates a new one. |
|
Archived work items |
Archived work items (on either side) don't sync until they're restored. |
|
Settings locked after syncing |
Once a sync rule has synced work items, its connectors and scope can't be changed. See Settings Locked After Work Items Are Synced. |
Fields
Only the following fields can be mapped. Other fields don't appear in the field mapping list.
|
Type |
Supported |
|---|---|
|
System fields |
Summary, Description, Work type, Priority, Resolution, Assignee, Reporter, Due date, Labels, Components, Fix versions, Affects versions, Environment, and time tracking (original and remaining estimate) |
|
Custom field types |
Text field (single line), paragraph (text area), number, date, date and time, URL, read-only text, select list (single and multiple choice), cascading select, radio buttons, checkboxes, labels, user picker (single and multiple), group picker (single and multiple), version picker (single and multiple), space picker, and Epic Name |
|
Not supported |
Among others: Sprint, Epic Link, Rank, Team, parent, subtasks, work item links, work logs, watchers, votes, security level, and fields added by other apps |
-
Direct copy matches values such as work type, priority and options by name. When names differ between the sites, use Value map.
-
Script transforms aren't available. Use Direct copy, Value map, Smart value or Static value.
Comments, attachments and status
|
Limit |
Details |
|---|---|
|
Attachment size |
Attachments larger than 200 MB never sync. They're skipped, not reported as failures. Your own size filter can't raise this limit. |
|
Comment formatting |
With Direct copy, comment formatting is kept. With a smart value template, the comment is sent as plain text, and formatting and embedded media are dropped. |
|
Author of synced content |
On the other site, synced work items, comments and attachments are created by the connector's account. On This Jira site, pulled changes are made by the Sync Bridge app. |
|
Status in team-managed spaces |
If several transitions lead to the same target status, Sync Bridge uses the first one Jira returns. |
|
Status transitions |
A status change only syncs if the target workflow has a transition from the current status to the mapped status. |
Product limits
|
Limit |
Value |
|---|---|
|
Trial |
Up to 2 connectors and 3 sync rules |
|
Sync history retention |
30, 90, 180 or 365 days. Default: 90 days. A daily cleanup removes older entries, and they can't be recovered. |
|
Sync history search |
Up to 20 work item keys at a time |
|
API tokens |
Up to 10 per sync rule. Expiration: 30, 60, 90 or 365 days, or never. Token names: up to 50 characters. |
|
Manual push, pull and retry |
Jira administrators only |
|
Configuration |
Jira administrators only |