Control trashed Rich Filters during DC to Cloud Migration
When performing incremental or phased migrations from Jira Data Center to Cloud using the Jira Cloud Migration Assistant (JCMA), a situation might arise where previously deleted Rich Filters, those moved to trash in the Cloud instance, are unintentionally migrated.
To address this, a dark feature flag has been introduced that lets you skip the migration of Rich Filters that were deleted in the Cloud, helping to prevent duplicated Rich Filters.
Feature Flag: com.qotilabs.jira.rf.cloud-migrate.skip-deleted-filters
Steps to enable the feature flag:
To enable the feature flag on your Jira Data Center instance:
Log in as a Jira System Administrator.
Navigate to
<BASE_URL>/secure/admin/SiteDarkFeatures!default.jspa– replace the <BASE_URL> with your instance base URL.Add the following flag:
com.qotilabs.jira.rf.cloud-migrate.skip-deleted-filtersEnsure the flag appears in the enabled features list, and then perform the migration.
When the flag is disabled (default):
Rich Filters that exist in the Cloud under the trash section will be remigrated during subsequent JCMA runs.
This is the default behavior introduced before this feature was added.
When the flag is enabled:
Rich Filters trashed on the Cloud will not be migrated again, helping to avoid duplicate or unwanted filter restoration during incremental or repeated migrations.
For more information on dark features, refer to https://confluence.atlassian.com/jirakb/how-to-manage-dark-features-in-jira-server-and-data-center-959286331.html