Skip to content

Allow groups to be migrated as new top-level groups

Problem to solve

When selecting groups to migrate from one instance of GitLab to another, the user is unable to select <root>, indicating that they want to migrate a group as a top-level group.

Moreover, if the destination instance has no top-level groups, the UI fails. This scenario is exacerbated by the fact that having no top-level groups is a common situation for users who just set up their new GitLab instance and are looking to migrate their groups over.

Proposed solution

The user should be able to migrate their groups as new top-level groups in the new instance. A new <root> choice in the destination dropdown should always be available so that the users are not forced to migrate their top-level groups as subgroups.

No-Parent_v1

→ Allow groups to be migrated as new top-level groups - Layout specs

→ Pajamas dropdown component specs (Figma file)

→ Pajamas forms component specs (Figma file)

This page may contain information related to upcoming products, features and functionality. It is important to note that the information presented is for informational purposes only, so please do not rely on the information for purchasing or planning purposes. Just like with all projects, the items mentioned on the page are subject to change or delay, and the development, release, and timing of any products, features, or functionality remain at the sole discretion of GitLab Inc.

Edited by 🤖 GitLab Bot 🤖