-
Type:
Bug
-
Resolution: Answered
-
Priority:
Medium
-
None
-
1
-
Severity 3 - Minor
-
Warranty
Issue Summary
When the source and destination sites have a large number of groups (>10,000), the "Groups with the same names exist on the destination" preflight check returns an unexpected error instead of completing successfully.
Steps to Reproduce
- Have >10,000 groups on the source/destination site
- Attempt to migrate Jira/Confluence space from Site A to Site B within the org
Expected Results
When group name conflicts are detected, the check should complete and present the following options:
Green light to proceed the migration, after clicking on "Merge groups" button:
![]()
Actual Results
From the logs, the check continues and completed. But UI shows the check fails with the following unexpected error:
We found an unexpected error and couldn't run this check. Try validating again or contact support if you continue to get this message
![]()
Unable to proceed the migration because "Merge groups" button is not selected.
Workaround
Contact Atlassian Support to get the list of duplicate groups and trigger "Merge groups" option.
- has a derivative of
-
CLOUD-12972 C2C Migration: Skip group name check for sites within same Org
- Gathering Interest