The roadmap below shows our future features that enhance the use of Backbone Issue Sync on Cloud. Each card features a label with an estimated time of arrival (Q2 2021) and a public Jira issue where available. We encourage you to use these Jira issues to subscribe for updates or provide input about your requirements regarding that feature
Sync Versions Project Configuration (Server ↔ Cloud)
Enable a full synchronization of Versions between projects, not only the issue. This is for a Server to Server/Cloud sync
Sync Versions Project Configuration (Cloud ↔ Cloud)
Enable a full synchronization of Versions between projects, not only on the issue. This is for a Cloud to Cloud sync.
BAC-137 - Sync Versions/Components Project configuration Open Q4 2021
The performance of Backbone issue sync on cloud for syncing issues is improved by 66%
BAC-1456 - Optimize sync performance under high load Released to Cloud Q3 2020
Support Data Residency for storing Backbone data.
Rate Limit Handling
Improve the way Backbone handles the rate limiting.
BAC-1460 - Handle rate limits of Jira Cloud Released to Cloud Q2 2021
Sync Component Project Configuration
Enable a full synchronization of Components between projects, not only the issue.
UI update and improvements
A migration to the latest Atlassian design with improvements to work easier and faster with Backbone.
Extension Mechanism for Cloud
Make it possible to create even more flexible field mappings, e.g. for custom fields.
BAC-1481 - Smart values in field mappings Open TBA
Show Sync Activity
Give admins more insights into the sync activity of Backbone. For example: how many issues are currently synced.
BAC-1193 - Show a detailed sync activity to the Backbone admin Open TBA
Control over Synchronization access
Give control which partner instance can view and edit the synchronization.
BAC-1049 - Make distributed configs available for cloud <> cloud/server Open TBA
Disclaimer on ETAs
We decided to include estimated times of arrival on most features listed above to give our users some planning security. However, please keep in mind that those timeframes are not guarantees, but rather our best guess given the information we currently have and are thus subject to change.