Planner role unable to read_code on private projects with default permissions

Summary

As a team member added to a private project with the Planner role, I am unable to view the project repository in the UI (read_code permission).

Steps to reproduce

• Add team member to private project with Planner role
• View private project repository as the team member with Planner role

Example Project

• https://gitlab.com/cguitarte-sandbox/demos/mlops-demo/-/tree/main
  • user: cguitarte-workshop - added with Planner role assigned

What is the current bug behavior?

See 404 error when viewing private project repo, Code links not visible in main nav.

What is the expected correct behavior?

Planners can see private project repo

Relevant logs and/or screenshots

Roles assigned to Project members

404 on repo view as Planner

Project view from an owner

Project view from Planner

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

Patch release information for backports

If the bug fix needs to be backported in a patch release to a version under the maintenance policy, please follow the steps on the patch release runbook for GitLab engineers.

Refer to the internal "Release Information" dashboard for information about the next patch release, including the targeted versions, expected release date, and current status.

High-severity bug remediation

To remediate high-severity issues requiring an internal release for single-tenant SaaS instances, refer to the internal release process for engineers.