Improve list of target (sub-)groups when transfering a repository

Problem to solve

We have one sub-group per customer project. Each sub-group stores only 5 repositories: Datasheet, Documentation, Specification, Hardware and Software. Many of these sub-group have a "libraries" and an "ipcores" sub-group, where we store the repositories of numerous Git submodules, which are referenced from the Hardware or Software sourcecode repository.

Project A
o- Datasheet
o- Documentation
o- Hardware
o- ipcores
|  o- Core 1
|  o- Core 2
o- libraries
|  o- Lib 1
|  o- Lib 2
o- Software
o- Specification

The Git submodule structure is as follows:

Software
o- libraries
|  o- Lib 1
|  o- Lib 2
o- Hardware
   o- ipcores
      o- Core 1
      o- Core 2

When I need to move a repository (GitLab project) from somewhere into a "libraries" or "ipcores" subgroup, I get dozens of results in the "transfer project" drop down. Even by filtering for the target, I get dozens of results for "libraries".

As my suggestion: In a first iteration, maybe yes, but not as a final result.

Further details

GitLab should offer a comprehensive list of groups that can serve as a target for a transfer operation.

Proposal

Replace the dropdown field with the tree view of groups from "groups" main menu. It has these advantages:

• show only personal groups
• search groups by name
• sort groups by different critera
• browse groups based on hierarchy

What does success look like, and how can we measure that?

Group tree view from "group" main menu:

Links / references

This is related to:

• gitlab-foss#53271 (moved)
• #15013 (closed)

/cc @jramsay ("transfer project" seams to be part of "Create" :) )