Issue Summary

Migrating from on-prem JSM, the custom field Customer Request Type, which is a locked field that has its custom field type as Customer Request Type, deliberately gets merged with the locked custom field in Cloud, Request Type, which has the same custom field type Customer Request Type.

Steps to Reproduce

1. Create a filter that references the custom field Customer Request Type
2. Create a JSM Project, add this custom field to that project via association with the project's screen
3. Create a Jira issue on that project, and populate the Customer Request Type custom field with any given value
4. Migrate that project to an Atlassian cloud site with JCMA

Expected Results

Filters have their JQL updated with the new custom field name.

Actual Results

• Customer Request Type values gets added to the Request Type custom field (seems intentional)
• Filters break because their JQLs reference the Customer Request Type custom field (seems unintentional)

The values of the Customer Request Type, like contexts and screens, are appended into the custom field Request Type in Cloud after migration.

The custom field Customer Request Type does not get migrated. Instead, its values are copied to the Request Type custom field.
This might cause JQL/Filters that use this custom field name to not bring the expected results.

Workaround

Currently, there is no automated workaround for this behavior. A workaround will be added here when available.

Meanwhile, to fix the broken JQLs, users must edit them manually and reference the Request Type custom field instead.