What you need to know before you restore a Jira Cloud backup on Cloud

On Atlassian Cloud instance, there is an identifier in Jira's Cloud database called Client Key that Tempo (any 3rd party add-ons) uses as reference to connect with Jira. Once you perform an import (restore a backup), this Client Key is updated with a new one and Tempo has lost the reference at this point. Atlassian is aware of this problem as we have raised this issue with them.

Because your Jira instance url and old client key already exist in our instance registry and we do not allow duplicate installation to avoid mixing data/instances, the old Tempo instance will not be able to recognize with new Jira client key.

To restore your Tempo data:

We need to do some legal process to get a snapshot of your data
We will send you the encrypted data file
We will have to manually disable/decommission the old client key & instance url configuration within our system, which will render your old Tempo data unusable. (Tempo data includes Accounts, Teams, Worklogs, Timesheet approvals, configuration, workload and holiday schemes, etc..)
You will have to re-install Tempo and start from fresh.
You will have to upload the old data onto your new Tempo instance with the Tempo Cloud REST API.