Deleted projects leave dangling state than can collide with new projects
Summary
Deleting a project in GitLab leaves state behind that can collide with a new project with the same name in the same group.
Steps to reproduce
- Create a new group with name "x"
- Create a new project with name "y"
- Select the Issues:Boards tab in the sidebar for project "x"/"y". You will be presented with an option to create a default set of lists for the board.
- Create the default boards
- Delete the project "x"/"y"
- Create a new project with name "y", the same as in step 2
- Select the Issues:Boards tab in the sidebar for project "x"/"y". You will not have the option to create a default set of lists for the board, and will instead see lists for "Open" and "Closed"
What is the current bug behavior?
The newly created project with the same name as the deleted project shows two lists, "Open" and "Closed"
What is the expected correct behavior?
The newly created project with the same name as the deleted project should show two lists "Open" and "Closed", with a UI element between them offering to create a set of default "best-practices" lists
Relevant logs and/or screenshots
(Paste any relevant logs - please use code blocks (```) to format console output, logs, and code as it's tough to read otherwise.)
Output of checks
n/a
Results of GitLab environment info
n/a
Results of GitLab application Check
n/a
Possible fixes
My best guess is that some state regarding the project is stored in the database with the / as the key, rather than the project ID. This adds the potential to look up stale data. The steps to reproduce are more of a symptom of the issue rather than the issue itself.