JCMA migration creates Permission Schemes in Cloud without mapping issue types to their corresponding templates

Description
The JCMA migration creates the DC Permission Schemes in Cloud without properly mapping Issue Types to their corresponding templates. This results in an incomplete configuration after migration.

Pre-conditions

• A Jira DC instance with configured Permission Schemes that include Mapping of Issue Types to Templates
• Migration performed using JCMA
• Target Cloud instance ready to receive migrated data

How to reproduce

1. Configure a Permission Scheme with Mapping of Issue Types to Templates in the source DC instance
   
2. Run an Xporter DC/Cloud migration using JCMA
3. Navigate to the migrated Permission Scheme
4. Check the Mapping of Issue Types to Templates

Actual result/Attachments

• Permission Schemes are created in the target instance
• Mapping of Issue Types to Templates are not preserved
  

Expected result
Permission Schemes should retain all Mapping of Issue Types to Templates after migration

Version

• Xporter 7.4.4-j9
• JCMA 1.12.52

Workaround
Manually reconfigure Issue Type to Template mappings after migration