How to migrate all dashboards with the Jira Cloud Migration Assistant (JCMA)
Platform notice: Server and Data Center only. This article only applies to Atlassian products on the server and data center platforms.
Purpose
This document provides instructions on how Jira dashboards can be migrated via Jira Cloud Migration Assistant (JCMA) to Atlassian Jira Cloud. For a comprehensive list of all objects that JCMA will/will not migrate, see here: What gets migrated with the Jira Cloud Migration Assistant.
- DO NOT ENABLE THIS FEATURE FOR EVERY MIGRATION PLAN
Migrate dashboards as the last part of the migration, using a dummy project to initiate migration
Dashboard migration assumes that all dependencies such as projects, filters, software boards, sprints, etc. are already migrated to the cloud. Otherwise, dashboard migration may fail with incomplete status and dashboard gadget failure may occur. Follow How to migrate all boards and filters with the Jira Cloud Migration Assistant (JCMA) | Atlassian Cloud | Atlassian Documentation for cross-project boards and all filters migration. Note that dashboards may be migrated regardless of dependency issues, but may not be rendered properly in the cloud.
IMPORTANT: Support, CMMs, and customers should be aware that feature flags are experimental. We’ll do our best to offer support if these feature flags break migrations. However, we can't guarantee fixes or incident responses. Feature flags don’t cover all edge cases. If using these feature flags is your only option, test your migrations thoroughly with the feature flags enabled. You should consider manual workarounds when facing issues with feature flags.
- To manage dark features you need to be a Jira administrator
- Available from JCMA RELEASE 1.6.2
Summary
JCMA dashboard migration currently supports:
Dashboard, dashboard share permissions, gadgets, and gadget user preference migration.
Re-migration
Dashboards will not be duplicated due to re-migration.
Gadgets may be duplicated. (See caveats for exceptions)
Fix missing dependency from the previous migration
Duplicate dashboard names will result in failure to migrate.
If gadget references (project, filter, custom field, etc) are deleted, dashboard re-migration will reconstruct the broken gadget without manual intervention.
Admin can delete a dashboard or its gadget to re-migrate. JCMA migration will create all missing items.
Solution
Jira dashboard migration is not enabled in JCMA by default. Dashboards may be migrated from Jira Server/Datacenter by using a dark feature. See Enable Dark Feature in Jira for instructions on how to use dark features
This should be the last step in the migration process, executed AFTER all projects are migrated, by using a dummy project to initiate migration.
- Navigate to URL: <Jira_URL>/secure/admin/SiteDarkFeatures!default.jspa
- Input dark feature: com.atlassian.jira.migration.dashboard-migration.feature
- Click Add
Limitations and Known Issues
No system dashboard support means admins will not be able to migrate their system dashboards from the server to the cloud.
No system dashboard support means admin will not be able to migrate their system dashboards from the server to the cloud.
No third party gadget support yet you could get the boards themselves migrated.
No support for favorite board feature.
Crucible Charts, Fisheye Charts, Bubble chart, Introduction gadget, and Fisheye Recent ChangeSets gadgets are not supported.
Some gadgets which used custom fields may not work completely but users can open them and fix them after migration.
Minor display differences may occur but they are not blockers in operation.
If JCMA fails to migrate some dashboards, the plan will be in
INCOMPLETEstatus. JCMA does not show migration progress of dashboard migration.
Error and Workarounds
During dashboard migration, JCMA tries to migrate everything it can. In the case of missing dependencies during the import phase, the related dashboard will still be migrated. However, it might not render properly depending on the errors. Please validate migrated dashboards on the Cloud side.
Example dashboard gadget when project dependency is missing
Workaround is to either
Manually fix the dashboard on the cloud side.
Contact support to debug which dependencies are missing. Fix them on the server side and trigger a dummy project migration again, so JCMA can fix the broken component during re-migration.