Introduction
Data residency refers to the ability to specify the geographic location where your data is stored and processed. This capability is crucial for organizations that must comply with local data protection laws, industry regulations, or internal policies requiring data to be stored in specific regions. By controlling data residency, you can ensure that sensitive information remains within the designated boundaries, enhancing security and compliance.
Key aspects of data residency include:
- Geographic control: you can select a specific region where your data will be stored. This is important for meeting regional data protection regulations.
- Compliance assurance: helps organizations comply with laws such as the GDPR in Europe, CCPA in the United States, or other local data protection regulations.
- Improved performance: by storing data closer to your users, you can reduce latency and improve application performance.
- Enhanced security: keeping data within specified geographic boundaries can reduce the risk of unauthorized access and data breaches.
Data Residency Overview
Data Residency is available for Jira, Jira Service Management, Jira Product Discovery, and Confluence with Enterprise, Premium, and Standard plans.
Data Residency gives you control over where your in-scope product data for Jira, Jira Service Management, Jira Product Discovery, and Confluence is hosted.
It allows you to choose whether it’s globally distributed or held in place in a defined geographic location, such as Europe or the US.
If you work in a regulated industry like finance, government, or healthcare, Data Residency may be a necessity for operating in a cloud environment. More generally, it can also help you meet company data management requirements.
Viewing where your Jira Data is Hosted
You can view where your in-scope product data is hosted from your organization's administration (you must have organization admin permissions to do this):
Go to admin.atlassian.com. Select the desired organization if you have more than one (Figure 1 - 1).
The Atlassian Admin screen will open (Figure 2). On the top menu, click Security (Figure 2 - 1). A side menu will open. There, click Data residency (Figure 2 - 2).
This will open the Data Residency screen for your organization. This screen lists:
- The products in your organization (Figure 2 - 3) and their status (Figure 2 - 5).
- The apps (Figure 2 - 6) and the app's statuses (Figure 2 - 7).
- The location of each product (Figure 2 - 4) and the AWS regions (Figure 2 - 4) the location corresponds with. If a product is pinned to a location, its in-scope data is held there. If data residency is available for your product, you can request to have its in-scope data moved and pinned to a new location.
- How many products have their location set (Figure 2 - 12).
- How many apps are eligible to be moved (Figure 2 - 13).
Moving Jira Data to Another Location
If Data Residency is available for your product, you can request to have your in-scope product data pinned to a new location. You may need to do this to meet company data requirements. Or, if you work in a regulated industry like finance, government, or healthcare, this may be necessary for operating in a cloud environment.
This section provides detailed information on how to request a data residency move, how the move will affect your product, and how to cancel your data residency move for apps.
The default Jira location for the data is the US, but that can change on Atlassian discretion. If you want to ensure your data is hosted on the US region we advise you to pin your data to the US region.
Scheduling a Data Residency Move
If data residency is available for your product, you can move it to one of the supported locations.
To schedule a data residency move:
Go to admin.atlassian.com. Select the desired organization if you have more than one (Figure 1 - 1).
The Atlassian Admin screen will open (Figure 2). On the top menu, click Security (Figure 2 - 1). A side menu will open. There, click Data residency (Figure 2 - 2).
In the Products table, click View details (Figure 2 - 9) in the line of the product that you want to move. A new screen will open (Figure 3). There, click the Set location button (Figure 3 - 1).
A new screen will open (Figure 4).
Review the information about the steps involved in moving a product. Click the Next button (Figure 4 - 1).
Select the location from the menu where you want to move your product (Figure 5 - 1) and click Next (Figure 5 - 2).
Select a move window option (Figure 6 - 1) and click Next (Figure 6 - 2).
Review the apps (Figure 7 - 1) and click the Next button (Figure 8 - 2).
Review your data residency move request details (Figure 8 - 1) and click Submit request (Figure 8 - 2).
You can cancel your scheduled Data Residency move except if your Data Residency move has started and is in progress.
Data Residency Operations
With Data Residency, you can control where your data is stored. Xray fully supports Data Residency.
Currently, Atlassian supports a combined move of a product and Xray.
Moving your Xray Data to Another Location
Data Residency for Marketplace apps is currently in beta. This might impact the performance of these apps.
If you experience a sudden degraded performance in a Marketplace app in the coming weeks, we recommend going to the Your Apps tab (Figure 9 - 1), after entering admin.atlassian.com, and updating any apps (Figure 9 - 2) with the upgrades available.
App Statuses
Before you request a Data Residency move for Xray, you must understand the different app statuses.
Xray offers the ability to pin and move data between locations. There are four app statuses:
Pinned
Xray is already pinned to the product location and store data in the same location.
For example, say you have Confluence pinned to the USA location and install an Xray pinning to the USA. If Xray is installed after the product is pinned, it is also moved to the USA location. Xray would show up in the Pinned tab (Figure 10 - 2).
Eligible
For Xray to be eligible (Figure 10 - 1) for a Data Residency move, it must:
Support data pinning in the same location as the product.
Support data movement between locations.
Not be currently pinned to the same location as the product.
Not Eligible
If Xray is showing as Not eligible (Figure 10 - 3) for data residency move, it can be because the area selected is not supported for Data Residency in the same location as the product.
No Action Available
If you have apps that have no action available for a data residency move (Figure 10 - 4), it is because some app partners specify that their apps either:
- Only store data within the Atlassian product.
- Do not store any data at all.
Requesting a Data Residency Move for Xray
Go to admin.atlassian.com. Select the desired organization if you have more than one (Figure 1 - 1).
The Atlassian Admin screen will open (Figure 2). On the top menu, click Security (Figure 2 - 1). A side menu will open. There, click Data residency (Figure 2 - 2).
In the Data Residency table (Figure 1), click View details (Figure 1 - 9).
Check the Eligible tab (Figure 10 - 1).
If you have eligible apps, click the Move eligible apps button (Figure 10 - 5).
Review the information about the steps involved in moving your eligible apps and click Next.
Review the apps and click Next.
Select the 24-hour move window and click Next.
Review your app data residency move details and click Submit request.
- Data Residency move for Marketplace apps must be requested, at least, three days in advance.
- Xray might already be pinned to your selected region, even if you haven’t explicitly chosen that region. Xray might have been pinned during installation or pinned there to optimize performance. You can move your Xray data to another location of your choice, provided Xray supports your preferred location.
Xray Locations
At the launch, Xray supports data residency in the following locations:
- United States.
- Europe (Frankfurt).
- Australia (Sydney).
Data Residency Move for Xray and the Impact on Your Product
While Xray is moving your eligible app data to the requested location, the product will be offline, and your users will not be able to access it. This move can be scheduled up to three days in advance and takes up to 24 hours for all apps to move.
You should plan for your product to be offline for 24 hours during an app move. When you request a data residency move for Xray, you select a 24-hour move window. Atlassian provides this 24-hour window for Xray to move the app. Xray aims to complete your move within this window, but we cannot guarantee the exact time of the move as it depends on the size of the customer data.
As soon as the move is complete, your Atlassian product and Xray will be back online and you'll be notified by email.
When moving your data to a new region, the file dates will be updated to reflect the date of the transfer. We are working on a solution to preserve the original dates during this process.
If you have any questions, please contact Xray Support.
Canceling a Data Residency Move for Apps
You can cancel a data residency move as long the respective process active status is MOVE SCHEDULED. You can’t cancel a move after the status has changed to MOVE IN PROGRESS.
To cancel a data residency move:
Go to admin.atlassian.com. Select the desired organization if you have more than one (Figure 1 - 1).
The Atlassian Admin screen will open (Figure 2). On the top menu, click Security (Figure 2 - 1). A side menu will open. There, click Data residency (Figure 2 - 2).
Find the product in the data residency table and click View details (Figure 1 - 9).
Check the Eligible tab (Figure 10 - 1).
Find the app for which you want to cancel the Data Residency move, and click Cancel move.