Migration best practices for Rich Filters for Jira Dashboards DC to Cloud

Learn to troubleshoot migration errors and resolve issues with status indicators and progress percentages on the migration details page.

Before you start

• Review the migration guide: →Migration to Cloud.

How to read migration logs?

System admins can access logs from the migration details page → Rich Filters for Jira dashboards → View logs.

Navigate to <Jira Base URL>/secure/migration-app-action.jspa#/monitor, and look for the recent migration. Click View details to view the app migration process.

Open

Scroll to the bottom of the screen to find the app, and click the Menu icon () and select View logs.

Open

Let’s see an example below:

Line #2 provides detailed migration information:

Processed (64%); rich filters: 3230/3230 migrated; dashboards: 228/2137 migrated (1895 not mapped, 14 failed

The message says that:

• 3230/3230 rich filters migrated - All rich filters were successfully migrated

• 228/2137 dashboards migrated - Only 228 out of 2137 dashboards were migrated

• 1895 not mapped - These dashboards weren't selected in JCMA, so they weren't migrated (this is expected behavior with Smart Migration)

• 14 failed - These dashboards encountered errors during migration

For a better understanding of not-mapped dashboards, it appears that not all the projects/dashboards were selected as part of the migration – that's why it shows 1895 dashboards as unmapped, and the reason why they are not migrated. To confirm the selection part, you can check the top of the screen of this migration page, which has details about the projects/filters/dashboards selected for this specific migration. When you select specific projects/dashboards, Jira only sends the dashboards associated with those selected projects. Dashboards outside this scope won't have mapping, so the system counts them as "not migrated," which affects your success percentage.

You can identify the 14 failed dashboards from the logs themselves to better understand them. Line #4 lists dashboard IDs from DC to Cloud (example: 23524->10290). In most cases, the dashboards failed due to a permissions issue.

How to migrate the failed dashboards?

To migrate those 14 failed dashboards from the above example, you can follow one the following ways:

• Option 1: Change the dashboard share configurations in Cloud to let the app edit them, then re-run the migration ( by running a new migration that only enables the app should give the same results).

• Option 2: Delete the failed dashboards on Cloud, modify the dashboard share configurations in DC, then run a new migration with “All dashboards” and the app enabled.

The correctly migrated rich filters and dashboards remain unchanged, and no duplicates are created.

Permissions

• The permissions of these failed dashboards can be changed to:

  • remove all the project role shares (from both Viewers and Editors)

  • share with logged-in users (Viewers)
    
    

  This allows the app to edit the dashboards on Cloud. Once the dashboard migration is complete, you can restore the desired share permissions on these 14 dashboards on Cloud.

How to migrate the unmapped dashboards?

To migrate all 1895 unmapped dashboards from our example, run a new migration for the app with a simple placeholder project, choosing All Dashboards in the configuration screen.

Ongoing issues:

1. Failed dashboards usually result from permissions issues. The logs show that dashboards fail when the app tries to add permissions and bulk edit them. Here's the typical error:

   Error migrating dashboard java.lang.RuntimeException: bulkEditDashboard errors: {12979=BulkEditActionError[errors={}, errorMessages=[Invalid type given. Should be one of [USER, PROJECT, GROUP, PROJECT_ROLE, GLOBAL, AUTHENTICATED]]]} at com.qoti.rfc.jira.JiraDashboardService.bulkEditDashboard(JiraDashboardService.java:280) com.qoti.rfc.service.MigrationDashboardsService.loadCloudDashboard(MigrationDashboardsService.java:303)

We opened a ticket with Atlassian developer support → ECOHELP-69403, and their team will continue investigating this issue as part of JRACLOUD-95037. Meanwhile, follow the steps in How to migrate the failed dashboards as a workaround for successful migration.

2. Cloud allows a maximum of 20 gadgets per dashboard. If your data center has more gadgets configured, either:

   • check with Atlassian support to increase the limit on Cloud

   • remove the unused/unimportant gadgets in DC
     The error looks like:

     Cannot add another gadget. The maximum number of gadgets the dashboard can hold has been reached."],"errors":{}}" for Dashboard: id=16685, name=Scrumchamps and Northstar- Anurag

      

3. Cloud supports a maximum of 7,500 Rich Filters, while Server/DC has unlimited capacity. To learn more, see Feature parity – Cloud vs Data Center comparison | Rich Filters Global Functionality. Contact us if you need to increase the Cloud limit before starting migration. Note that even with the default 7,500 limit, all your Rich Filters can still migrate successfully.