<!--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> - [Work on this issue](https://contributors.gitlab.com/manage-issue?action=work&projectId=278964&issueIid=425184) - [Close this issue](https://contributors.gitlab.com/manage-issue?action=close&projectId=278964&issueIid=425184) </details> <!--IssueSummary end--> This issue will reuse the Project-level MR approval rules component for Group level, with relevant UI changes needed. * Ensure the frontend has the necessary data on the Project level (Project > Settings). * UI changes: display lock/message if there are any Group level rules) See [this comment](https://gitlab.com/groups/gitlab-org/-/epics/11451#note_1559373884) for additional context. # Frontend work * Add a lock to the component added in https://gitlab.com/gitlab-org/gitlab/-/issues/425181 * Add a tooltip with "Inherited setting" per proposal of @msedlakjakubowski in https://gitlab.com/gitlab-org/gitlab/-/issues/425433/designs/project_with_inherited_group_level_mr_approval_rules.png#note_1565347340  ### Availability and Testing Additional feature specs: - Ensure that if group level approval rules are present, project level approval rules are locked/have a message (see https://gitlab.com/gitlab-org/gitlab/-/issues/425181 for additional tests) Regression testing, please ensure associated MR is labelled with ~"pipeline:run-all-e2e" and `e2e:package-and-test` job is passing.