Issue : JCMA  version 1.12.61
JCMA currently exports project role actors via Jira role APIs (including role defaults) and migrates the global "Default Members" configuration. This results in multiple groups being unexpectedly added to all Jira/JSM project roles in Cloud after migration.

Current Behavior:
JCMA exports all project role actors including global default role members.

During migration, these default members are applied across all projects in the Cloud destination

Customers discover unexpected group additions across all spaces post-migration.

There is no option to skip default role members during migration.

Expected Behavior:
JCMA should NOT apply global/default project role members during migration
OR provide an option to exclude default role members from migration.
This behavior should be clearly documented.

Customer Impact:
Customer completed sandbox/production migration and discovered unexpected role member additions.

No way to prevent this without the temporary workaround (removing default role members before migration)

 
Workaround:
Temporarily remove default project role members before initiating the migration.

Customer Ask:
Fix the logic in a future JCMA version and document the limitation/behavior clearly.