Allow Management of Project Aliases via Project Settings
Everyone can contribute. Help move this issue forward while earning points, leveling up and collecting rewards.
Release notes
Problem to solve
As a Project Owner, I'd like to be able to Create/Read/Update/Delete ProjectAlias assignments via the project settings UI. Today, this is possible via the Project Aliases API (docs), but only as an instance administrator.
Proposal
Allow a Project Owner CRUD permissions to ProjectAliases (today it's only accessible for Instance Administrators, and only via API). This may have security or abuse considerations. Do we do collision checking on namespaces today? i.e. we should not allow a group owner to specify a redirect for an existing project or namespace.
Add a section to the Project Settings UI to CRUD a project alias.
Intended users
Who will use this feature? If known, include any of the following: types of users (e.g. Developer), personas, or specific company roles (e.g. Release Manager). It's okay to write "Unknown" and fill this field in later.
Personas are described at https://about.gitlab.com/handbook/marketing/product-marketing/roles-personas/