| Note |
|---|
The automatic migration of rich filter gadgets with JCMA is supported by Rich Filters for the Jira Dashboards starting with version 2.1.0. We recommend you use the latest Data Center app version to perform your migration. |
...
Starting with the version 2.1.0 of the app, both the rich filters and the rich filter gadgets can be automatically migrated using the Jira Cloud Migration Assistant (JCMA). More precisely, during a migration run, JCMA first migrates your Jira data and then orchestrates the migration process for our the Rich Filters app.
| Anchor | ||||
|---|---|---|---|---|
|
...
This preparatory step is necessary in order to avoid having prevent some rich filter dashboards that fail from failing to migrate due to inadequate insufficient permissions.
Currently, Atlassian doesn’t provide specific support for the migration of third-party gadgets with JCMA (cf. see MIG-1937). The Rich Filters app uses the existing Jira Cloud APIs to implement the rich filter gadget migration. One of these APIs has a bug that, for particular dashboard share configurations, makes it impossible for the app to give itself the permission to edit the Cloud dashboards (cf. see JRACLOUD-84000), resulting in dashboards that fail to migrate.
...
Until Atlassian fixes this bug (or provides specific support for the migration of third-party gadgets), you need to implement the following workaround in the source DC Jira Server/Data Center instance:
Identify the rich filter dashboards that are shared with at least one project with an explicit project role selected (in Edit and Share Dashboard / Viewers or Editors) => For these dashboards you need to remove all the project role shares (from both Viewers and Editors). If you preferwish, you can also share these dashboards with logged-in users (Viewers).
Among all Identify the rich filter dashboards, including the ones treated in step 1 above, identify the dashboards that are shared with at least one group (in Edit and Share Dashboard / Viewers or Editors, including among those treated in step 1 above) and are not shared with logged-in users => You need to share these dashboards with logged-in users (Viewers).
These steps will allow our the Rich Filters app to work around the Jira API bug and give itself the permission to edit the Cloud dashboards during the migration. Once After the dashboard migration is finishedcompleted and verified, you can restore the appropriate permissions of the Cloud dashboards.
...
In this step, you need to check that all the rich filters gadgets have been correctly migrated.
Reminder: The preparatory step Step #2 - Prepare your dashboards for the migration is necessary to prevent some rich filter dashboards from failing to migrate due to insufficient permissions.
It is expected that Server/Data Center app features that are not supported on Cloud will result in misconfigured gadgets.
For example, gadgets configured with features from the Rich Filters::Time Tracking Dashboards app extension will show an error in the migrated dashboard. The misconfigured gadgets will need to be manually reconfigured or deleted in the Cloud instance.
...