Issue Summary

The "Data Transfer" tool (for cloud-to-cloud migrations) should clearly show the full list of users and groups that will be migrated (for selective copy) and why they’re included.

Users may assume only a specific set of users and groups will be migrated, but due to dependency expansion (like other users in Jira boards/filters and Confluence followers/followees in spaces), more users and groups than expected can end up on the destination instance.

A pre-migration report with all of the users and groups that will be migrated is helpful.

Steps to Reproduce

1. Start a Jira cloud-to-cloud Copy Plan in the Data Transfer tool
2. Select a subset of projects to migrate.
3. Select a limited set of users/groups
4. Include boards and filters for those projects (where some of those boards/filters are shared with additional groups not explicitly selected)
5. Run through pre-checks and review the plan.
6. Execute the migration

Expected Results

Before clicking “Copy data”, the UI should:

• Show the complete, final list of groups that will be migrated (after resolving dependencies from boards/filters, etc), and clearly distinguish:

• • Groups explicitly selected by the admin, vs.

• • Groups pulled in automatically due to dependencies.

• • Optionally, provide per-group explanation (e.g. “included because used in filter ABC-Filter, shared with project XYZ”).

Actual Results

The pre-migration flow doesn’t clearly indicate all the additional groups that will be migrated due to boards/filters, etc. Also, numbers on the post-migration UI can differ from the numbers in the post-migration CSV.

After migration, admins may see more groups than expected.

Support has advised that the UI summary for a plan shows how many users and groups were processed during that specific run (i.e., created or updated in that run), whereas the CSV report shows a snapshot of what exists in the destination after the plan

Workaround

Currently there is no known workaround for this behavior.