Timesheets, Planner, and Financial Manager apps support data residency for the following regions:
-
EU / Germany (Frankfurt): “https://app.eu.tempo.io”
-
United States: “https://app.us.tempo.io”
Hosting Jira and Tempo in different regions will not cause issues, provided that all Tempo apps stay together. However, region requirements depend on whether you are moving Jira or Tempo data:
-
Moving Jira to a new region: Supported. Tempo can remain in a different region as long as all installed Tempo products (Tempo Core, Timesheets, Capacity Planner, and Financial Manager) are hosted in the same region as one another.
-
Moving Tempo data to a new region: Requires Jira to be hosted in the exact same region where the Tempo apps are being pinned to move.
To migrate your Tempo apps data to a specific location, contact Atlassian. Please do not delete any of your Tempo apps, unless requested to do so by Atlassian or the Tempo support team.
Tempo data residency migration typically takes 30 minutes to complete.
After migrating your app data:
-
Slack integration will need to be re-enabled for the new region.
-
OAuth apps and API integration tokens will need to be recreated so they correspond with the new region.
If you experience any issues or have questions about moving your Tempo data, please contact the Tempo Support Team.
What’s not Migrated?
Tempo Automation data from integrated apps is not migrated. These apps from which Tempo gathers activity and event data (such as MS 365 calendar) must be reconnected after migration.
Troubleshooting
-
If you uninstalled/reinstalled a Tempo app and have lost data, stop using the Tempo app and contact the Tempo Support Team immediately.
-
Timesheets, Planner, and Financial Manager all need to be installed in the same region to work together. If you already have one of our apps installed and the installation of an additional app fails, please contact our Tempo Support Team so they can investigate.
Learn More
To learn more about data residency or migrating your data to a specific location, please see the following guides from Atlassian: