Preserve user permissions on imported groups
What does this MR do?
As per a question in ZD (internal use only)
If I migrate a group to a new gitlab-installation, it might happen that the users do not exist beforehand. Therefore it is important that once the members are created, they get access to the group
The documentation doesn't mention that users that are members of an exported group actually need to exist in the GitLab instance before a group is imported, in order for those users to be correctly associated as members in the destination group.
I've added a note so we have this in the docs.
Related issues
Author's checklist
-
Follow the Documentation Guidelines and Style Guide. -
If applicable, update the permissions table. -
Link docs to and from the higher-level index page, plus other related docs where helpful. -
Apply the documentation label.
Review checklist
All reviewers can help ensure accuracy, clarity, completeness, and adherence to the Documentation Guidelines and Style Guide.
1. Primary Reviewer
-
Review by a code reviewer or other selected colleague to confirm accuracy, clarity, and completeness. This can be skipped for minor fixes without substantive content changes.
2. Technical Writer
-
Optional: Technical writer review. If not requested for this MR, must be scheduled post-merge. To request for this MR, assign the writer listed for the applicable DevOps stage.
3. Maintainer
-
Review by assigned maintainer, who can always request/require the above reviews. Maintainer's review can occur before or after a technical writer review. -
Ensure a release milestone is set. -
If there has not been a technical writer review, create an issue for one using the Doc Review template.