Settings migration error due to mapped issue types may cause the migration to fail

If the migrated projects do not contain all the issue types that are configured as requirement or defect in Xray, then the migration will fail when importing the settings because Xray is not able to populate the mappings due to those issue types not existing in the cloud.

Workaround:

In the server, add all the mapped issue types in the Xray Issue Type Mapping settings to at least one of the migrated projects (these can be removed after the migration). This ensures that the issue types are migrated and present in cloud when Xray tries to import the settings