Transferred subgroup creates parent group with no members
Transferring a subgroup both after selecting a parent group and also without selecting a parent group to transfer to will turn that subgroup into a parent group and remove all members from it.
Any member who was an owner of the original parent group will still be able to view the transferred group if
No parent group was selected in the transfer dropdown menu. In both cases, this prevents the use of this new group or its removal without GitLab.com admin intervention.
Steps to reproduce
- Create a group on GitLab.com.
- Create a subgroup within the parent group you created.
- Optionally, create a project within your subgroup.
- Invite a member to your subgroup as any role.
- Visit the
Settings > General > Path, transfer, removesection of the subgroup.
- In the transfer group section click
- Observe that you're now looking at the same subgroup which has been converted to a parent group with no members. If you were previously an owner of the old parent group you can now also still view the contents of the new parent group if it was transferred with
No parent groupselected.
Initially created the following structure (group, subgroup, project):
What is the current bug behavior?
After transferring, we're left with
subgroup-678 as parent groups with
project-678 and any other projects within that subgroup as a part of the latter with owners of
tw-group-678 able to see the contents of
subgroup-678 but not do anything with it.
What is the expected correct behavior?
That ownership be inherited to the subgroup being transferred.
Relevant logs and/or screenshots
Member list of the subgroup after it was transferred into its own parent group as viewed by the user that initiated the transfer.
Output of checks
This bug happens on GitLab.com
ZD: https://gitlab.zendesk.com/agent/tickets/110085 (Internal)