<!--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=118881) </details> <!--IssueSummary end--> ### Problem to solve <!-- What problem do we solve? --> Gitlab users not getting notified when a merge request WIP is resolved and is ready for review/approval. ### Intended users <!-- Who will use this feature? If known, include any of the following: types of users (e.g. Developer), personas, or specific company roles (e.g. Release Manager). It's okay to write "Unknown" and fill this field in later.--> Gitlab users that are members of a project with an open merge request. ### Further details <!-- Include use cases, benefits, and/or goals (contributes to our vision?) --> Currently for **all** members of a project to receive a notification that a merge request WIP is resolved and is ready for review/approval, the merge request creator must assign the merge request to all members that they intend to notify. For projects with a large number of members this is waste of time and unrealistic to assign the merge request to **all** members of the project. We are also seeing merge requests that need approving going unnoticed because there is no notification when unassigned. ### Proposal <!-- How are we going to solve the problem? Try to include the user journey! https://about.gitlab.com/handbook/journeys/#user-journey --> At the project level add option "Resolve merge request WIP"  ### Permissions and Security <!-- What permissions are required to perform the described actions? Are they consistent with the existing permissions as documented for users, groups, and projects as appropriate? Is the proposed behavior consistent between the UI, API, and other access methods (e.g. email replies)?--> The user wanting to turn this notification on will need to be a member of the project; this align with the permission rules already in place for the `Custom notification events`. ### Documentation <!-- See the Feature Change Documentation Workflow https://docs.gitlab.com/ee/development/documentation/feature-change-workflow.html Add all known Documentation Requirements here, per https://docs.gitlab.com/ee/development/documentation/feature-change-workflow.html#documentation-requirements If this feature requires changing permissions, this document https://docs.gitlab.com/ee/user/permissions.html must be updated accordingly. --> ### Testing <!-- What risks does this change pose? How might it affect the quality of the product? What additional test coverage or changes to tests will be needed? Will it require cross-browser testing? See the test engineering process for further help: https://about.gitlab.com/handbook/engineering/quality/test-engineering/ --> I expect no risks for this change. This is an optional notification, so anyone not wanting to be notified does not have to opt out; this is only an opt in notification. ### What does success look like, and how can we measure that? <!-- Define both the success metrics and acceptance criteria. Note that success metrics indicate the desired business outcomes, while acceptance criteria indicate when the solution is working correctly. If there is no way to measure success, link to an issue that will implement a way to measure this. --> Success is seen when a notification is seen in the merge requests notifications in the banner at the top of the UI.  ### What is the type of buyer? <!-- Which leads to: in which enterprise tier should this feature go? See https://about.gitlab.com/handbook/product/pricing/#four-tiers --> Should be available for all tiers, as it is simply a notification option. ### Links / references https://gitlab.my.salesforce.com/001610000120Exq