Issue Summary

JCMA does not update custom field names in migrated filters

Steps to Reproduce

1. In Cloud have a custom field of one type, radio buttons for example
2. On Server have a custom field with same name but is a different type, select list for example
3. On Server create board for project being migrated. Edit filter's JQL to include custom field name somehow
4. Migrate project containing that custom field from Server to Cloud with JCMA

Expected Results

New custom field created with (Migrated) appended to custom field name to address conflicts
Migrated JQL filters are updated with (Migrated) appended to custom field names so they continue to function after migration

Actual Results

New custom field created with (Migrated) appended to custom field name to address conflicts
Migrated JQL filters are not updated and are potentially broken

Workaround

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