Question
How can dashboard ownership be handled with a service account when migrating Custom Charts for Jira Data Center to Jira Cloud with JCMA?
Answer
A service account here is a single-user account that has all required permissions in both Jira Data Center and Jira Cloud and has logged in to the Jira Cloud site at least once. The account in Jira Data Center must match the account on Jira Cloud (same email address). It temporarily owns the dashboards so Custom Charts can recreate the gadgets during the migration.
Before starting, make sure Custom Charts for Jira Data Center is 7.8.4 or later, and that Custom Charts is set to Needed in cloud in JCMA (Jira Settings > System > Migrate to Cloud > Assess your apps).
1. Identify the dashboards and their owners in Jira Data Center
-
Tempo Support can share example SQL queries that list the dashboards containing Custom Charts gadgets, their owners, and the number of gadgets per owner. Contact Tempo Support through the Support Portal to request them.
-
The queries were originally prepared for a specific earlier migration, so your database administrator may need to adapt them. Tempo does not adjust or maintain them.
2. Prepare the service account
-
Create or select the account, and make sure it has the required permissions in both Jira Data Center and Jira Cloud, and that it has logged in to the Jira Cloud site at least once.
3. Change dashboard ownership in Jira Data Center
-
Use ScriptRunner for Jira Data Center to set the service account as owner of every dashboard identified in step 1. ScriptRunner has a built-in option for changing dashboard owners in bulk; see Adaptavist's documentation.
4. Run the JCMA migration
-
Run the migration with Custom Charts marked as needed in Cloud.
5. Restore the original owners on Jira Cloud
-
Use ScriptRunner for Jira Cloud, for example, the example script for changing dashboard ownership.
6. Review the results
-
In the Custom Charts admin settings, open the Cloud Migration tab and check the Gadget Status Breakdown column.
Tempo does not write or debug scripts. For help with ScriptRunner, see Adaptavist support.