Cloud Roadmap
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
Planned | In Progress | Shipped |
---|---|---|
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 TBA | Initiate synchronization from Cloud to Server/DC Enable to also set up the sync on the cloud side when syncing between cloud and on-prem Q1 2023 | Improve Syncing Performance The performance of Backbone issue sync on cloud for syncing issues is improved by 66%
|
Data Residency Support Data Residency for storing Backbone data. Q2 2023 | Rate Limit Handling Improve the way Backbone handles the rate limiting.
| |
Sync Component Project Configuration Enable a full synchronization of Components between projects, not only the issue. TBA | UI update and improvements A migration to the latest Atlassian design with improvements to work easier and faster with Backbone. Q2 2021 | |
Extension Mechanism for Cloud Make it possible to create even more flexible field mappings, e.g. for custom fields.
| Search for Backbone attributes with JQL You are now able to search for the issue sync status, remote key, last send and received by JQL.
| |
Show Sync Activity Give admins more insights into the sync activity of Backbone. For example: how many issues are currently synced.
| 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.
| |
Control over Synchronization access Give control which partner instance can view and edit the synchronization.
| ||
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.