How Does Data Residency Work in Backbone?

Backbone Issue sync supports data residency. In this article we’ll dive deeper into what data is stored where. For more general information about Data Residency, please check out the FAQ.

Tenant Related Data

The following data are considered tenant related data:

1. Global configuration settings, e.g. who can access Backbone.

2. Tenant information, e.g. base url, secret to access the Jira instance.

3. Cached Jira information, e.g. fields, issue types, projects.

Same-region syncs

The global configuration settings are stored locally. The tenant information and cached Jira information are stored globally unless you are syncing two projects on your own instance. In that case, these are stored in the region of your instance.

Cross-region syncs

The global configuration settings are stored locally. The tenant information and cached Jira information are stored globally.

Synchronization Related Data

The following data are considered synchronization related data:

1. Configuration of the synchronization

2. Pairing information of issues, attachments, comments, and versions

3. Troubleshooting data

Same-region syncs

All synchronization related data stays in the region. For example, if you are syncing between two instances in the EU, the synchronization related data stays in the EU.

Cross-region syncs

All synchronization related data is stored globally. For example, if you are syncing between an instance in the US and an instance in the EU, the data is stored globally.