<!--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=18307) </details> <!--IssueSummary end--> As a part of fixing the MR desktop notifications for the new MR widget https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/11734, I found that we have a good base here to start providing notifications for MR status **beyond** the pipeline status. For example, instead of just notifying `Pipeline is now [pipeline_status]`, we could send notifications for an MR that was just closed or merged. We could even go as far as assignee or label changes, but I think we should choose the most important statuses. ____ Regarding approach, we should build a status-notificationData map where "notificationData" is an object with keys `title` and `message` that we can render into strings for the `notifyMe` function. This can all be within a `NotificationService` in `vue_merge_request_widget/services`. /cc @dimitrieh