<!--IssueSummary start--> <details> <summary> Everyone can contribute. [Help move this issue forward](https://handbook.gitlab.com/handbook/marketing/developer-relations/contributor-success/community-contributors-workflows/#contributor-links) while earning points, leveling up and collecting rewards. </summary> - [Close this issue](https://contributors.gitlab.com/manage-issue?action=close&projectId=278964&issueIid=436426) </details> <!--IssueSummary end--> <!--- Please read this! Before opening a new issue, make sure to search for keywords in the issues filtered by the "regression" or "type::bug" label: - https://gitlab.com/gitlab-org/gitlab/issues?label_name%5B%5D=regression - https://gitlab.com/gitlab-org/gitlab/issues?label_name%5B%5D=type::bug and verify the issue you're about to submit isn't a duplicate. ---> ### Summary If a code owner has `Reporter` permissions or lower on a project, they are shown as an eligible approver. They aren't able to approve the merge request (which is expected), but why are they showing as an eligible approver? ### Steps to reproduce 1. Add a code owners file to an existing project targeting `/path/to/stuff @<username>` 2. Add the user as a member to the project and give them the `Reporter` role 3. Make a change within `/path/to/stuff` and create an MR 4. In the merge request, the user with the `Reporter` role is shown as an eligible approver in the MR approvals widget. 5. If you sign in as the user in question, they can see themselves as an eligible approver in the MR approvals widget, but the `Approve` button is missing (that is expected) Do note the same issue occurs if you add a group as a member to the project.  ### Example Project N/A ### What is the current *bug* behavior? Code owners that aren't eligible to approve an MR are appearing as such in the merge request widget ### What is the expected *correct* behavior? Code owners that aren't eligible to approve an MR should not appear as such in the merge request widget ### 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 <!-- If you are reporting a bug on GitLab.com, uncomment below --> <!-- This bug happens on GitLab.com --> <!-- /label ~"reproduced on GitLab.com" --> #### Results of GitLab environment info <!-- Input any relevant GitLab environment information if needed. --> <details> <summary>Expand for output related to GitLab environment info</summary> <pre> (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`) </pre> </details> #### Results of GitLab application Check <!-- Input any relevant GitLab application check information if needed. --> <details> <summary>Expand for output related to the GitLab application check</summary> <pre> (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) </pre> </details> ### Possible fixes <!-- If you can, link to the line of code that might be responsible for the problem. -->