Overview
Tempo currently supports data residency in the EU (Germany) and the US. This means that Tempo data can only be hosted in these two regions. Please see https://help.tempo.io/timesheets/latest/data-residency for more info.
Customers who use Atlassian products (e.g., Jira Software, Jira Service Management) can choose to host their Atlassian data in other supported regions (e.g. Switzerland, Australia etc, see: https://support.atlassian.com/security-and-access-policies/docs/understand-data-residency/#What-are-locations-and-AWS-regions ).
However, Tempo must always follow Atlassian’s regional setup, meaning Tempo can only be pinned to the EU or US if the customer’s Jira instance is also in the same region.
To pin Tempo to a specific region (EU or US), Jira must already reside in that same region first.
Only after Jira and Tempo are aligned in region, Jira can later be moved to another location, if desired.
Example Scenarios
Scenario 1: Jira needs to reside in Switzerland, Tempo in the US
If a customer currently has Tempo data in the US and wants to move Jira to Switzerland, without changing Tempo’s region:
-
Pin Atlassian (Jira) to Switzerland, by following these steps: https://support.atlassian.com/security-and-access-policies/docs/move-data-to-another-location/
Result:
-
Jira data resides in Switzerland
-
Tempo data remains in the US
Scenario 2: Jira needs to reside in Switzerland, Tempo in the EU
If a customer currently has Tempo data in the US and wants Jira in Switzerland but Tempo in the EU, the process is:
-
Pin Atlassian (Jira) to the EU: https://support.atlassian.com/security-and-access-policies/docs/move-data-to-another-location/
-
Pin Tempo to the EU: https://support.atlassian.com/security-and-access-policies/docs/moving-your-marketplace-apps-data-to-another-location/
-
Pin Atlassian (Jira) to Switzerland: https://support.atlassian.com/security-and-access-policies/docs/move-data-to-another-location/
Result:
-
Jira data resides in Switzerland
-
Tempo data resides in the EU