Prevent exceeding allowed projects during Group Migration
Problem to solve
When performing a migration of a group that includes one or more projects, it is possible that the user reaches their project limit during the import. This would mean that the user would not be allowed to create any additional projects and the import would fail, leaving the group partially migrated and the user confused about how to proceed.
Proposed solution
Check the user's project allowance against the number of projects in each group. If the user is not allowed to create as many projects as exist in the group, that group would not be importable.
Desired user experience
- Groups that cannot be imported should still be displayed in the group list, but without the ability to import (Import button disabled or not visible)
- The user should be able to tell why a group is not available for import. A short message, such as
Maximum project count exceeded
is sufficient. - This message could be added to the pre-migration check report.
Future iterations
To improve the user experience in this scenario, the user could be presented with the ability to select as many projects to import from a group as they are allowed, enabling them to fully utilize their allowance. This solution would build on the ability to multi-select the groups to be imported and allow the user to also multi-select the project they would like to migrate.
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.