<!--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=545424) </details> <!--IssueSummary end--> MR: Pending <!--NOTE: For context on MR heading, see: https://handbook.gitlab.com/handbook/engineering/development/dev/create/remote-development/index.html#relationship-of-issues-to-mrs--> ## Description When changes happen in group membership and make users inherited members, users who were in an MR approval group disappear. There may be other membership changes that cause a similar where the approvers list is emptied. There is no audit event indicating that the users were removed, but we have audit events when they are added to an approval group. This makes debugging when and by whom they were removed hard to track. If there's an event to update the MR approval group list when users are removed, we can log that event and which user was removed. The users usually come back and **Current behavior:** No project audit event when users are removed due to changes in Direct/Inherited membership role. **Expected behavior:** When the membership structure changes, I would expect an audit event as below: `Removed User Jane Doe from approval group on Example rule` **Steps to reproduce:** * Add two users to a project * Add an approval rule with the two users, * Move these users to be inherited members of the parent group instead of direct members. * Their membership changes, they are removed from the approval rule, but no audit event indicates that update, whether expected or not. **Additional information:** Customers affected by an "unknown" cases of disappearing MR approvers where logs would have helped * [Ticket](https://gitlab.zendesk.com/agent/tickets/604104) [604104](https://gitlab.zendesk.com/agent/tickets/604104) * [Ticket 604547](https://gitlab.zendesk.com/agent/tickets/604547) As a \[user or stakeholder\], I want \[goal or objective\] so that \[reason or benefit\]. <!--TODO: What kind of issue is this? Please uncomment and include one of the following: /label ~"type::feature" /label ~"type::bug" /label ~"type::maintenance"--> <!--OPTIONAL: Is this a feature/enhancement? - Please describe the impact this feature/enhancement will have on the user experience and/or the product as a whole. - Provide a user story to illustrate the use case for this feature/enhancement. Include examples to help communicate the intended functionality.--> <!--OPTIONAL: Is this a bug? Please uncomment and include the following: - **Current behavior:** - **Expected behavior:** - **Steps to reproduce:** - **Additional information:** please include VSCode version, browser dev tool logs, etc that might be helpful to debug the issue!--> ## Acceptance criteria TODO: Fill out (required) - [ ] \[Describe what must be achieved to complete this issue.\] - [ ] \[If applicable, please provide design specifications for this feature/enhancement.\] - [ ] \[If applicable, please list any technical requirements (performance, security, database, etc.)\] ## Implementation plan TODO: Fill out or delete (optional)\ \[Provide a high-level plan for implementation of this issue, including relevant technical and/or design details.\] <!--NOTE: Feel free to expand with more sections and headers as needed--> <!--DO NOT TOUCH BELOW-->