<!-- Use this template as a starting point for deprecations. --> ### Deprecation Summary In GitLab 13.0, we added new routes to the replication details views for projects and designs along with redirects for the old versions of the routes. In https://gitlab.com/gitlab-org/gitlab/-/blob/master/ee/config/routes/admin.rb#L49-51: ``` # Old Routes Replaced in 13.0 get '/projects', to: redirect(path: 'admin/geo/replication/projects') get '/designs', to: redirect(path: 'admin/geo/replication/designs') ``` ### Breaking Change <!-- Does this MR contain a breaking change? If yes: - Add the ~"breaking change" label to this issue. - Add instructions for how users can update their workflow. --> ### Affected Topology This may affect admins who have bookmarked the old routes and still use them. However, we anticipate this to be a very small number of users. <!-- Who is affected by this deprecation, Self-managed users, SaaS users, or both? This is especially important when nearing the annual major release where breaking changes and removals are typically introduced. These changes might be seen on GitLab.com before the official release date. --> ### Affected Tier Premium, Ultimate <!-- Which tier is this feature available in? * Free * Premium * Ultimate --> ### Checklist - [ ] @mention your stage's stable counterparts on this issue. For example, Customer Support, Customer Success (Technical Account Manager), Product Marketing Manager. - To see who the stable counterparts are for a product team visit [product categories](https://about.gitlab.com/handbook/product/categories/) - If there is no stable counterpart listed for Sales/CS please mention `@timtams` - If there is no stable counterpart listed for Support please @mention `@gitlab-com/support/managers` - If there is no stable counterpart listed for Marketing please mention `@williamchia` - [x] @mention your GPM so that they are aware of planned deprecations. The goal is to have reviews happen at least two releases before the final removal of the feature or introduction of a breaking change. ### Deprecation Milestone %14.8 <!-- In which milestone will this deprecation be announced ? --> ### Planned Removal Milestone %"15.0" <!-- In which milestone will the feature or functionality be removed and announced? --> ### Links <!-- Add links to any relevant documentation or code that will provide additional details or clarity regarding the planned change. Also, include a link to the removal issue if relevant. --> <!-- Label reminders - you should have one of each of the following labels. Use the following resources to find the appropriate labels: - https://gitlab.com/gitlab-org/gitlab/-/labels - https://about.gitlab.com/handbook/product/categories/features/ --> <!-- Populate the Section, Group, and Category --> <!-- Choose the Pricing Tier(s) --> <!-- Identifies that this Issue is related to deprecating a feature --> <!-- Add the ~"breaking change" label to this issue if necessary -->