FAQ about Data Residency

Data residency gives you control over where your in-scope data is hosted. In some industries data residency is a necessity for operating in a cloud environment, as it allows you to choose a defined geographic location, such as Europe or the US. Please see Atlassian’s own documentation to learn more.

Currently, Backbone Issue Sync supports data residency in the US, EU and DE (Germany):

• US: In-scope data is hosted within the AWS region in Oregon, USA.

• EU: In-scope data is hosted within the AWS region in Frankfurt, Germany.

• DE: In-scope data is hosted within the AWS region in Frankfurt, Germany.

However, Atlassian also offers additional regions for data residency and plans to introduce more. If you’re interested in having your app data stored in a different region please let us know via help@k15t.com.

Please see our K15t Data Security Statement for an overview of the in-scope data that is stored in a defined region. This includes Account Data, Session Data, Support Data, Customer Uploaded Data, Operation Data and more.

When you install the app it will be tied to the Jira region that is defined (if supported by Backbone Issue Sync).

If the Jira data residency region defined is not supported by Backbone Issue Sync it will not be possible to move the app data.

The answer is dependent on what region your Jira instance is running. For instance, if the Jira instance has data residency pinned to a specific region that we don’t support, it will always default to the “global” region, which is the US for Backbone Issue Sync.

However, Jira also has the concept of running an instance in a specific region without being data residency pinned to it (you can’t choose this region). If this is the case for your instance, when you install the app, Jira will choose the closest supported region ie. EU or US.

For more technical insights into these scenarios please see Atlassian’s own developer documentation.

If you change the region for your Jira instance the app data will remain in the region that the Jira instance was initially used. You have to initiate the app data migration in order for it to be moved between regions.

Related FAQs:

• Check out → Where is my app data stored if my Jira is pinned to a region not supported by Backbone Issue Sync?

• Check out → How can I move app data?

1. Firstly, ensure that Jira is defined in the required region - you need to follow Atlassian’s documented steps and request a data residency move.

2. Then, proceed to move the app data to your defined region - you can learn more here.

   • Note that while the app is migrating, your synchronizations will be stopped. Please inform your partners to not start the sync to prevent potential duplication of issues.

3. After this, the data is migrated. Please note, only Marketplace apps that support the defined data residency region can then be migrated together - it is not possible to pick and choose which apps are moved.

Currently, the following K15t cloud apps support data residency:

• Backbone Issue Sync

• Scroll Word Exporter

• Scroll PDF Exporter

• Scroll HTML Exporter

• Scroll Exporter Extensions

If you use other K15t apps that don’t currently support data residency but you would like them to, please let us know via help@k15t.com.

Please check out the following: How Does Data Residency Work in Backbone?

Please check out the following: How Does Data Residency Work in Backbone?

By default, all your app data is in the US (as it is now as well) and you therefore don’t need to take action. If you want to move your data over, you can follow the steps laid out here.

More information can also be found in the release notes.