When you migrate from Jira Data Center to Jira Cloud, your presets, work schedules, and report setup migrate with the app — no manual recreation.
Time in Status calculates its reports from your Jira issue history in real time, rather than keeping a separate copy of that history. When you migrate the app from Jira Data Center to Jira Cloud with the Jira Cloud Migration Assistant, your app configuration migrates with it, so you keep your setup instead of rebuilding it.
Two items still need manual setup in Cloud: permissions and dashboard gadgets.
Before you begin
-
Applies when you migrate Time in Status from Jira Data Center to Jira Cloud.
-
You run the migration with the Jira Cloud Migration Assistant, which requires Jira administrator access.
-
When you choose what to migrate, select Time in Status among the apps.
-
Running the migration again does not create duplicate presets, work schedules, or reports.
What migrates automatically
Your Time in Status configuration is part of the same migration you run for Jira. When migration finishes, these are available in Cloud with no manual steps:
-
Presets — your saved report configurations in Save & Load on the app's main page.
-
Report setups you have not saved as a preset.
Set up what does not migrate
After migration, set up the two items that do not carry over:
-
Review and adjust your permissions to match the access you need.
-
Add your Dashboard gadgets back to your Jira dashboards and configure each one.
Limitations
-
Migration does not bring across your Dashboard gadgets or your permissions — set both up again in Cloud (see above).
-
Time in Status does not backfill or repair issue history. Reports reflect only the issue history present in Cloud.
If you need help or want to ask questions, please contact SaaSJet Support or email us at support@saasjet.atlassian.net
Haven’t worked with the add-on yet? Give it a try