Reorganize Group-level Packages and Registries Settings for Improved Clarity and User Experience

Everyone can contribute. Help move this issue forward while earning points, leveling up and collecting rewards.

• Close this issue

Details

Currently, the packages, container registry, and dependency proxy settings are spread across different sections, which can lead to confusion and difficulty in finding specific settings.

We are updating the Project-level settings in #500217 (closed), and want to do the same to Group-level.

Proposed Changes

Group Level Settings

Package Registry

• Duplicate packages
• Package forwarding

Container Registry

• Enable/disable feature
• Lifecycle policies

Value Proposition

1. Improved User Experience: By grouping related settings, users can more easily find and manage the needed features, reducing time spent navigating through settings.
2. Clarity in Feature Management: This reorganization separates the settings for different types of registries and proxies, making it easier for users to understand which settings apply to which feature.
3. Reduced Confusion: The clear categorization will help prevent users from accidentally modifying settings for the wrong feature, potentially avoiding misconfigurations.
4. Easier Onboarding: New users and platform engineers will find it easier to understand the available 6. Future-Proofing: By clearly separating these features, it becomes easier to manage future changes or deprecations (like the noted deprecation of the dependency proxy for packages in 2025).

Next Steps

1. Create mockups of the new settings layout for both project and group levels.
2. Plan the implementation, considering any potential impacts on existing workflows or automations.
3. Update documentation to reflect the new organization of settings.

By implementing this reorganization, we aim to enhance the overall user experience for GitLab users working with packages and registries, making these powerful features more accessible and manageable.