📘 What you will learn here
On this page you will learn what each Sync Bridge license edition (Evaluation, Standard and Advanced) includes: how often scheduled pull can run, whether you can use the Sync Trigger API, and how long sync history is kept. You also learn what happens to your sync rules and sync history when you change edition.
Sync Bridge has two paid editions, Standard and Advanced. A free trial is the Evaluation edition. Your edition comes from your Atlassian Marketplace license. You choose it when you buy or change your subscription in Settings > Apps > Manage apps.
📊 Compare editions
|
Feature |
Evaluation (free trial) |
Standard |
Advanced |
|---|---|---|---|
|
Scheduled pull |
At most once a day |
At most once an hour |
As often as every 5 minutes |
|
Sync Trigger API (push and pull) |
✅ Included |
❌ Not included |
✅ Included |
|
Sync history retention |
Up to 1 year |
Up to 6 months |
Up to 1 year |
|
Connectors |
Up to 2 |
No limit |
No limit |
|
Sync rules |
Up to 3 |
No limit |
No limit |
|
Everything else |
Included in every edition: push and pull, field and status mapping, smart values, comments and attachments, manual and Jira event triggers, manual pull, the Sync Bridge panel, Sync history, JQL search, and duplicating, exporting and importing sync rules. |
||
The Evaluation edition includes every Advanced feature, so you can try them all during your trial. Only scheduled pull is slower: it runs at most once a day.
⏱️ Scheduled pull
Your edition sets the shortest time between two scheduled pulls of the same sync rule. It applies only to the Scheduler pull trigger. Push, manual pull and pulls started through the Sync Trigger API aren't limited.
|
Edition |
Fastest schedule |
A blank cron expression means |
Fastest preset you can pick |
|---|---|---|---|
|
Evaluation |
Once a day |
About once a day |
Daily at 9:00 |
|
Standard |
Once an hour |
Once an hour |
Hourly |
|
Advanced |
Every 5 minutes |
Every 5 minutes |
Every 5 minutes |
In the sync rule editor:
-
Presets that are faster than your edition allows are disabled. Hover over one to see why.
-
If you save a cron expression that runs more often than your edition allows, the editor shows, for example: Your Standard license pulls at most once an hour. Choose a slower schedule, or leave it blank.
-
Leave the cron expression blank to pull as often as your edition allows. A blank schedule speeds up on its own when you upgrade.
-
The preview under the cron expression shows the next three pulls that will really run, after your edition's limit.
-
On Advanced, a cron expression that runs more often than every 5 minutes can be saved, but runs every 5 minutes.
🔌 Sync Trigger API
The Sync Trigger API is included in Advanced and Evaluation. It covers both API push and API pull.
On Standard:
-
The API trigger switch in the push and pull triggers is disabled and shows Needs an Advanced license.
-
You can't create API tokens. You can still revoke existing ones.
-
Every call to the API returns
403with the message The web trigger (API) needs an Advanced license. Upgrade the Sync Bridge license to use it.
📜 Sync history retention
A Jira administrator sets how long sync history is kept under Sync history > Settings: 1 month, 3 months (default), 6 months or 1 year.
-
On Standard, 1 year (Advanced license) is shown but can't be selected.
-
Saving a longer period than your edition allows shows: Your license keeps the sync history for at most 6 months. Upgrade to Advanced to keep it for 1 year.
For details, see Sync History.
🔄 When you change edition
The new edition applies as soon as Atlassian updates your license. You don't need to change anything in Sync Bridge.
Upgrade (Standard to Advanced, or trial to a paid license)
-
The new limits apply right away. Sync rules with a blank cron expression pull more often on their own.
-
A rule that was waiting for its next daily pull from the trial is pulled at the next scheduler check, without waiting for the rest of the day.
-
On Advanced, the API trigger becomes available. Rules that already had the API trigger turned on accept API calls again.
-
When a trial becomes a paid license, the limits of 2 connectors and 3 sync rules no longer apply.
Downgrade (Advanced to Standard, or trial to Standard)
Nothing is deleted from your sync rules, and no rule is turned off. But some settings now do less:
|
Setting |
What happens after the downgrade |
|---|---|
|
A pull schedule faster than once an hour |
It's kept, but runs at most once an hour. The editor shows Your Standard license pulls at most once an hour, so this schedule runs at most once an hour. You can still save the rule with this schedule. You can't change it to another schedule that is faster than once an hour. |
|
The API trigger |
It stays turned on in the rule, but every API call is refused with |
|
Sync history kept for 1 year |
The daily cleanup keeps only the last 6 months, even if the setting still says 1 year. Older entries are removed in the next daily cleanup and can't be recovered. |
Sync history entries older than 6 months are removed in the first daily cleanup after you downgrade to Standard, and can't be recovered. Plan for this before you downgrade.
Trial ends without a paid license
Syncing and editing pause until you buy a license. Your data is kept. See Installation Guide.
📦 Duplicated and imported sync rules
A rule you duplicate or import is a new rule, so it gets only what your edition allows:
-
On Standard, the API push and API pull triggers are turned off. If push or pull then has no trigger left, its manual trigger is turned on, so the rule stays valid.
-
A pull schedule faster than your edition allows is set to your edition's fastest preset: Hourly on Standard, Daily at 9:00 on Evaluation.
Each change is shown as a warning: after you duplicate a rule, and on the Review rules step of an import. See Duplicate, Import and Export Sync Rules.
➡️ Related pages
-
Installation Guide: free trial and what happens when a license expires.
-
Create a Sync Rule: pull triggers and schedules.
-
Sync Trigger API: push and pull from other services.
-
Current Limitations: all fixed limits.