<!--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=334286) </details> <!--IssueSummary end--> <!-- This template is a great use for issues that are feature::additions or technical tasks for larger issues.--> ### Proposal <!-- Use this section to explain the feature and how it will work. It can be helpful to add technical details, design proposals, and links to related epics or issues. --> Support notifications for MR reviews and remind them in Slack if MRs are pending their review and approvals. Some paid tools provide this kind of thing, it might be a sign that there’s value in it. |Tool|GitLab SaaS|GitLab Self-Managed|GitHub|Details| | --- | --- | --- |--- | --- | | https://code-dog.app/| ✅ | ❌| ✅ | [code-dog self-managed deprecation](https://code-dog.app/blog/post/server-discontinued/) | | https://pullpanda.com/|❌ | ❌ |✅ |[acquired by GitHub](https://pullpanda.com/github) | | https://pullreminders.com/| ✅| ❌| ✅| | | https://www.eleminder.com|✅ | ❌| ✅| | |https://www.npmjs.com/package/@zekker6/slack-gitlab-mr-reminder |✅|✅|❌|self-host solution looks like it might work with self-hosted instances given one of the arguments is GITLAB_EXTERNAL_URL | GitHub's Slack integration also supports [Scheduled Reminders](https://github.com/integrations/slack#scheduled-reminders). And, [more info about personal reminders](https://docs.github.com/en/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-your-membership-in-organizations/managing-your-scheduled-reminders). <img src="/uploads/25bd00985200470398bc996918e44ec8/image.png" height="300"> #### Workarounds An alternative approach to addressing this problem is by setting up email notifications from GitLab to forward to your Slack personal DMs. Here are the steps: 1. Navigate to a DM with yourself in Slack by hitting cmd+k or ctrl+k and type your name.  2. Click your name at the top and navigate to the “Integrations” pane. 3. Click “Send emails to this conversation”. - Optional: click “Customize Email Appearance” with an image (such as the gitlab logo) and message name.  4. Copy the email and navigate to Preferences (upper right user icon) → Emails in GitLab. Add the email address provided by Slack.  5. Click the link in the email sent to your new channel (in Slack) in order to verify the email. This will require expanding the email message within the Slack notification.  6. Navigate to Preferences → Notifications and change your “Notification Email” to the Slack one you just added.  7. You should now get all personal notifications to this Slack channel. You can use a combination of Slack’s notification settings and Gitlab’s to ensure that this channel isn’t too noisy and only receives notifications that require your immediate attention. Note: Alternatively, you can create a private channel and send messages there. #### Customer feedback about our Current Slack Integration - The users are notified by all MRs opened in a project, not just the ones where they are approvers/reviewers (related to [#12855](https://gitlab.com/gitlab-org/gitlab/-/issues/12855)) - Automatic reports of pending MRs and configurable reminders are not supported. #### Customer Impact - [Premium, SaaS, 10 seats](https://gitlab.com/gitlab-org/gitlab/-/issues/334286#note_1083572657) - [Premium, SaaS, ? seats](https://gitlab.my.salesforce.com/0014M00001peCFXQA2) - [Premium, SaaS, 1000 seats](https://gitlab.my.salesforce.com/0014M00001lbKNk) <!-- Consider adding related issues and epics to this issue. You can also reference the Feature Proposal Template (https://gitlab.com/gitlab-org/gitlab/-/blob/master/.gitlab/issue_templates/Feature%20proposal%20-%20detailed.md) for additional details to consider adding to this issue. Additionally, as a data oriented organization, when your feature exits planning breakdown, consider adding the `What does success look like, and how can we measure that?` section. -->