Promoting milestones from project to group level does not create forwarding rules for URLs
Summary
When promoting a milestone from project to group level, the links to the original milestone simply show a 404 page instead of forwarding the browser to the corresponding group milestone.
Steps to reproduce
- Create a project milestone and copy it's URL
- Promote the milestone to group level
- Check that the URL of the project milestone shows a 404 page
Example Project
- Project: https://gitlab.com/mlegner-test-group/test/-/milestones
- Milestone URL before promoting: https://gitlab.com/mlegner-test-group/test/-/milestones/1
- Milestone URL after promoting: https://gitlab.com/groups/mlegner-test-group/-/milestones/1
What is the current bug behavior?
Links to project milestones stop working when the milestones are promoted to group level.
What is the expected correct behavior?
Forwarding rules should ensure that using (old) links to project milestones forward the browser to the new milestone at group level.
Relevant logs and/or screenshots
Output of checks
This bug happens on GitLab.com
Possible fixes
After promoting a project milestone to group level, its number is not reused for milestones created afterwards, so forwarding should not be a fundamental issue. See this test project, where I did the following:
- Created a first milestone (assigned number 1)
- Promoted the milestone number 1 to group level
- The URL for milestone number 1 stopped working
- Created a second milestone; the second one was assigned number 2