Copying data to a Sandbox environment

Problem

We created a new Sandbox instance from the Production environment, but the Tempo data was not copied.

We need the Sandbox to have the same Tempo Timesheets data as Production.

Solution

Copying data from a Production environment to a Sandbox one is considered a cloud-to-cloud migration.

Unfortunately, there isn’t an “easy” way to copy the data from one side to the other.

Please also refer to this Atlassian article, which mentions that plugin data (App data) is not migrated using any of the migration methods Atlassian offers.

In case you would like to try to migrate Tempo worklogs from the first Cloud instance (production) to the second Cloud instance (sandbox) yourself, you will need to do the following:

Irrespective of which migration method you execute, all Jira worklogs will be migrated to the target Cloud instance from the source Cloud instance.
To avoid duplicate worklogs in Jira, all those worklogs need to be deleted with the JIRA REST API before proceeding with the next steps!

1. Export all Tempo worklogs from the first Cloud instance with the Tempo REST API. The reason for this is that all Tempo worklogs reside in a separate database on Cloud, and very limited, anonymized worklog data is synced back to Jira. (Jira has no information about the worklog owner). The only way to export worklogs with the real worklog owner and worklog description is with the Tempo REST API.

2. Remove all worklogs from Jira that were migrated with the issues to the target instance, using the Jira REST API 

3. Import the worklogs that were exported from Tempo to the target Cloud instance with the Tempo REST API, JIRA REST API or a JIRA native .csv import.