Issue Summary

Currently app custom field types are not migrated by JCMA. Only locked connect app custom fields can be migrated https://developer.atlassian.com/platform/app-migration/tutorials/migrating-app-custom-fields/ However many apps allow customers to create their own custom fields using an app provided custom field type. There is no automated way to migrate these custom fields today.

Updates

We have introduced migration of custom field types for Forge apps. https://developer.atlassian.com/platform/app-migration/tutorials/connect-vs-forge-migrations/#forge-custom-fields-vs-connect-custom-fields-migration 

Steps to Reproduce

1. Install an app that provides their own custom field types
2. Create a new custom field with the app's custom field type
3. Update custom field configuration so it shows up in the relevant issues
4. Migrate project with issues using that custom field
5. Observe migrated project issues are missing custom field

Expected Results

Customer created custom fields using app custom field types are migrated to cloud with JCMA

Actual Results

Customer created custom fields using app custom field types are not migrated to cloud with JCMA 

Workaround

Customers have to manually recreate their app custom fields in cloud and manually export custom field values from server and import them in cloud.