On new project, modifying project name field updates project slug even if slug is customized
Summary
When creating a new project, a project slug is automatically generated from the project name. But, if the slug is customized and then the user goes back to edit the project name, the custom slug is overwritten by the auto-generated value.
Steps to reproduce
- Create a new project.
- Fill in a project name. Notice that a slug is generated.
- Replace the generated slug with something else.
- Edit the project name again.
Example Project
N/A
What is the current bug behavior?
The value of the project slug is replaced with a generated value based on the project name.
What is the expected correct behavior?
If the user has customized the slug, editing the project name should not replace the custom slug value. It is very frustrating to customize the slug, only for GitLab to overwrite it on subsequent changes to the project name.
Relevant logs and/or screenshots
**A new project with a custom slug named “a-custom-slug”.
**Project name is changed. The custom slug is lost, and replaced with an auto-generated value.
Output of checks
This bug happens on GitLab.com.
Results of GitLab environment info
N/A
Results of GitLab application Check
N/A