Issue Summary

N/A

Steps to Reproduce

1. Do a migration where one project role is assigned to multiple projects
2. During the migrating JCMA will create one project role per project even though the default members are exactly the same for all the copies. 

After trying to repro these steps, the issue was NOT reproducible hence striked them. The above was probably an intermittent issue that is now fixed.

There is however an issue where the ProjectRoles are duplicated when the number of default members in them change. Steps

1. Create a new Destination site.
2. Do a PbP migration (using JCMA) from a source. If there are existing default members in any group in the source, they would be duplicated in the destination.

The above is however an expected behaviour since the number of default members in the groups have changed.

To fix this issue, make sure that the default members in the source and destination are exactly same before migrating.

Expected Results

As per https://support.atlassian.com/migration/docs/how-the-jira-cloud-migration-assistant-links-your-data/ Project roles shouldn't be duplicated if the default members are same. 

Actual Results

Project Roles are split per project 

Workaround

Currently there is no known workaround for this behavior. A workaround will be added here when available
1. To prevent this issue, make sure that the default members in the source and destination are exactly same before migrating.

2. To fix this issue, replace all occurances of the old Group (without the Migrated Tag) with the latest migrated Group(with the latest Migrated Tag).
 Then delete the old Group after making sure everything works fine.