Interrupting a CCMA plan to add users to a group, then resuming plan, migration will not reflect the last change

Issue Summary

This is reproducible on Data Center: (yes)

When creating a new migration plan using CCMA, the customer chooses their Migration Options, selects one or a few spaces, chooses to migrate Only users related to the selected spaces, and then Checks for Errors.

For some reason the customer closes the migration at the Pre-migration Checks page (even after Checks have been done and OK) so the customer returns to Confluence admin page and decides to add one more user to a group that is related to the space selected in the previous migration plan, after this membership, the customer goes back to resume the migration keeping the same selection that they have selected and then Run it.

After the migration is completed without any error, the customer realizes the last user added to the group has not been migrated to the Confluence cloud.

This also occurs whether doing membership or creating a new group and granting permission to the selected space for migration. The group won’t be migrated.

Steps to Reproduce

1 - Create a new migration plan using CCMA

2 - Choose their Migration Options, select one or a few spaces, and choose to migrate Only users related to the selected spaces

3 - Check for errors

4 - At the Pre-migration Checks page after the checks have been done, close the migration plan page

5 - Returns to Confluence admin page and add one more user to a group that is related to the space selected in the previous migration plan

6 - Go back to resume the migration keeping the same selection that has been selected previously and then Run the migration.

Expected Results

Any modifications occurring during the migration plan must be reflected in the migration consequently the user membership should be migrated to the Confluence Cloud.

Actual Results

After the migration is completed without any error, the last user added to the group has not been migrated to the Confluence Cloud.

Workaround

A new migration plan should be created even if renaming the current migration plan does not work.