Details
-
Suggestion
-
Resolution: Unresolved
-
None
-
None
-
1
-
Description
Issue Summary
When performing a scoped user S2C migration, users who owned content, no longer have access to the space, at the time of migration, are not migrated
This is reproducible on the Data Center: Yes
Migration Type: server to cloud
Steps to Reproduce
- On Confluence server create a Space
- Allow permissions to the space to a group with few users ( eg: Admin+UserA)
- User A creates new content, PageA
- Admin removes UserA permission from the Space.
- Create a Migration Plan->Add the Space -> Select Only Users related to selected spaces -> Run The Migration
- Once Migration is complete, go to cloud site and check the user migrated and the pages
Expected Results
The UserA who does not have space permission be migrated and listed in User management with no product access ( admin.atlassian.com) and an user profile exist for UserA
Actual Results
The content (PageA) associated with the users who do not have permission (UserA) is migrated and user is Unlicensed, and also NOT listed in the User management (admin.atlassian.com)- no user profile exist for the Unlicensed UserA.
Workaround
Re-grant the user space permission on source and re-migrate
OR
Migrate all users.
Attachments
Issue Links
- is cloned from
-
MIG-1849 CCMA Group Page restrictions are dropped with scoped user/group migration if the group does not have space permissions
- Gathering Interest