Migrate from Rich Filters Server/Data Center to Cloud

Contents:

1. Introduction

The Rich Filters for Jira Dashboards app uses two different types of data that need to be migrated:

1. The configuration of the rich filters;

2. The configuration of the rich filter gadgets used in dashboards.

It is, of course, possible to migrate the app data manually, by recreating in the target Cloud instance the same configuration as in the source Server/Data Center instance. Consider this approach if you have few rich filters and rich filter gadgets to migrate, especially if you intend to use the migration as an opportunity to change some of your Jira and/or app configuration. There are no specific instructions for the manual migration of the app data, since it is a straightforward process. The rest of this page concerns the automatic migration of the app data.

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 app.

2. Automatic migration of the app data

Step #1 - Install required software

On your source Jira Server/Data Center instance, ensure you have installed the following:

• Rich Filters for Jira Dashboards version 2.1.0 or above, preferably the latest DC version;

• Jira Cloud Migration Assistant (JCMA) latest version.

On your target Jira Cloud instance, ensure you have installed and licensed the Rich Filters for the Jira Dashboards Cloud app.

Step #2 - Assess your apps

The first step in preparing a JCMA migration is Assess your apps on the Migration Assistant home screen—more information is available here. In this step, you must choose which apps to migrate to the Cloud.

• You need to mark Rich Filters for Jira Dashboards as Needed in cloud.

• If you also use rich filter extension apps, you must mark them all as Not needed in cloud.

On Cloud, the functionality provided by Rich Filters::Service Management Dashboards is available as part of the main Rich Filters for the Jira Dashboards app. Hence, when migrating the main rich filters app, the data provided by this rich filters extension is also migrated. Currently, the functionality provided by Rich Filters::Time Tracking Dashboards is not supported on Cloud.

Step #3 - Configure JCMA to migrate all filters and dashboards

Rich filters are based on (have a reference to) saved Jira filters. In order for this reference to be preserved during the migration, it is important that all the Jira filters that are referenced in rich filters be already migrated when the rich filters are migrated (see the section Migration best practices above).

The latest versions of JCMA provide support for Jira dashboard migration. The migration of dashboards with rich filter gadgets happens in two steps. In the first step, JCMA creates the dashboards on the target Cloud instance and migrates the native Jira gadgets (but not third-party gadgets). In the second step, the app migrates the rich filter gadgets on these dashboards. It is therefore important that all the dashboards that contain rich filter gadgets be already created by JCMA when the app data is migrated (see the section Migration best practices above).

Therefore, you should configure JCMA to migrate all Jira filters and all dashboards. To do this, in the JCMA migration configuration step Select dashboards, boards and filters you need to select the options Dashboards/All dashboards and Boards and filters/All filters and cross-project boards. For details see What gets migrated with the Jira Cloud Migration Assistant and How dashboards, boards and filters are migrated.

Step #4 - Enable app migration

To enable the migration of the app data, in the JCMA migration configuration step Select apps you need to select the option All - marked as Needed in cloud with a migration path. If you have other apps marked as “Needed in cloud”, make sure you consult the migration documentation of those apps as well.

Step #5 - Start the migration

Once you start the migration, JCMA first migrates your Jira data and then orchestrates the migration process for the Rich Filters app. When the app has finished the migration, your migration details screen will show a status and a progress percentage for the app. If all the rich filters and all the rich filter gadgets are migrated successfully, the status will be COMPLETE and the progress will be 100%.

3. Verification and adjustments

After the JCMA migration, the following steps must be completed on the destination Jira Cloud instance.

Step #1 - Check the base Jira filters

In this step, you need to check that all the migrated rich filters have a base Jira filter.

If any migrated rich filter doesn’t have a base Jira filter (i.e. the base Jira filter is NOT SET), you need to find out whether the corresponding Jira filter has been migrated in the same migration run as the rich filter (or in a previous but recent migration run—see the section Migration best practices above). If these conditions are met, yet the reference is broken, please create a support ticket so that our team can investigate the issue. If these conditions are not met, you will need either a) to identify the cause and fix the problem, and then run the migration again from scratch, or b) to manually create the missing Jira filter and/or set it as a base filter in the migrated rich filter. We remind you that rich filters can only be edited by their administrators (for more details, see Rights and Permissions).

SELECT rf.ID as rich_filter_id, rf.NAME as rich_filter_name, 
	   jf.id as jira_filter_id, jf.filtername as jira_filter_name, 
       jf.authorname as jira_filter_owner, jf.reqcontent as jira_filter_jql
FROM AO_24D977_QRFRFE0 rf INNER JOIN searchrequest jf ON rf.JIRA_FILTER_ID=jf.ID 
ORDER BY jira_filter_id, rich_filter_id;

SELECT rf."ID" as rich_filter_id, rf."NAME" as rich_filter_name, 
	   jf.id as jira_filter_id, jf.filtername as jira_filter_name, 
       jf.authorname as jira_filter_owner, jf.reqcontent as jira_filter_jql
FROM "AO_24D977_QRFRFE0" rf INNER JOIN searchrequest jf ON rf."JIRA_FILTER_ID"=jf.id
ORDER BY jira_filter_id, rich_filter_id;

Step #2 - Check the rich filter gadgets

In this step, you need to check that all the rich filters gadgets have been correctly migrated.

SELECT distinct d.id as dashboard_id, d.pagename as dashboard_name, d.username as dashboard_owner_username, 
       p.userprefvalue as rf_id, rf.NAME as rf_name
FROM portalpage d, portletconfiguration g, gadgetuserpreference p, AO_24D977_QRFRFE0 rf
WHERE d.id = g.portalpage
	AND g.id = p.portletconfiguration
	AND p.userprefkey = 'rf'
	AND p.userprefvalue = rf.ID
ORDER BY dashboard_id;

SELECT distinct d.id as dashboard_id, d.pagename as dashboard_name, d.username as dashboard_owner_username,
       p.userprefvalue as rf_id, rf."NAME" as rf_name
FROM portalpage d, portletconfiguration g, gadgetuserpreference p, "AO_24D977_QRFRFE0" rf
WHERE d.id = g.portalpage
    AND g.id = p.portletconfiguration
    AND p.userprefkey = 'rf'
    AND p.userprefvalue = cast(rf."ID" as varchar)
ORDER BY dashboard_id;

Step #3 - Check the JQL clauses

Update custom field ID references in JQL

If any of your JQL clauses in the configuration of rich filters or rich filter gadgets refers to a custom field using the cf[id] form, that reference is not automatically updated during the migration. For example, if on your Jira Server/Data Center you used the JQL query cf[...] is not empty, then the reference to the custom field ID is not translated when migrating to the Cloud. The JQL clause is migrated as-is, but the ID of the migrated custom field might be different on Cloud. Hence, if you used any such custom field references in your JQL, you must manually update them on Cloud.