Issue Summary

When performing a full data copy from production to a sandbox environment for Jira Software, Jira Service Management (JSM), and Confluence, group membership information is not being preserved. After the copy, users are present in the sandbox, but their group associations are missing or incomplete. This impacts permission schemes, space/project access, and overall user management in the sandbox environment.

Steps to Reproduce

1. In the production instance, ensure users are assigned to various groups in Jira, JSM, and Confluence.

1. Initiate a full data copy to a sandbox environment for all products.

1. After the copy completes, review group memberships in the sandbox for Jira, JSM, and Confluence.

Expected Results

All users should retain their group memberships in the sandbox, ensuring consistency with the production environment across Jira, JSM, and Confluence.

Actual Results

Users are present, but group memberships are either missing or don't match those in production in Jira, JSM, and Confluence.

Workaround

Currently, there is no known workaround for this behaviour.  Manual re-assignment of group memberships is required, increasing administrative overhead.