Group Merge request RSS link 404s

Summary

The RSS link for group wide Merge requests return 404. This is not a an issue with Issue RSS link nor for the the Merge requests RSS link for a single repo.

Steps to reproduce

Bad

  1. Navigate to the Merge requests page for a group, for example: https://gitlab.com/groups/gitlab-community/-/merge_requests
  2. Click either Actions drown down button or the ⋮ equivalent.
  3. Click the Subscribe to RSS feed item, in this case it would be https://gitlab.com/groups/gitlab-community/-/merge_requests.atom
  4. Page redirects to the atom url which returns 404.

Good

The same flow works for Issues https://gitlab.com/groups/gitlab-community/-/issues, https://gitlab.com/groups/gitlab-community/-/issues.atom

The Merge requests RSS link does work for a specific repo's activity: https://gitlab.com/gitlab-community/community-projects/merge-request-leaderboard/-/merge_requests, https://gitlab.com/gitlab-community/community-projects/merge-request-leaderboard/-/merge_requests.atom

What is the current bug behavior?

Link for a group's Merge requests RSS feed 404s

What is the expected correct behavior?

Link for a group's Merge requests RSS feed returns a vaild RSS/atom feed, just like how both group's Issues feed does and a specific/individual repo's Merge requests does too.

Relevant logs and/or screenshots

Output of checks

Results of GitLab environment info

Expand for output related to GitLab environment info 

(For installations with omnibus-gitlab package run and paste the output of: \`sudo gitlab-rake gitlab:env:info\`) (For installations from source run and paste the output of: \`sudo -u git -H bundle exec rake gitlab:env:info RAILS_ENV=production\`)

Results of GitLab application Check

Expand for output related to the GitLab application check 

(For installations with omnibus-gitlab package run and paste the output of: `sudo gitlab-rake gitlab:check SANITIZE=true`)

(For installations from source run and paste the output of: `sudo -u git -H bundle exec rake gitlab:check RAILS_ENV=production SANITIZE=true`)

(we will only investigate if the tests are passing)

Possible fixes

Edited by 🤖 GitLab Bot 🤖