Gitlab-Slack integration doesn't send events for changes in MR title or description
<!--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=235963) </details> <!--IssueSummary end--> <!--- Please read this! Before opening a new issue, make sure to search for keywords in the issues filtered by the "regression" or "bug" label: - https://gitlab.com/gitlab-org/gitlab/issues?label_name%5B%5D=regression - https://gitlab.com/gitlab-org/gitlab/issues?label_name%5B%5D=bug and verify the issue you're about to submit isn't a duplicate. ---> ### Summary We don't get slack notifications for changes in title/description of a merge request. We do get web hooks for changes in title/description, but not slack notifications ### Steps to reproduce 1. Setup slack integration using Incoming WebHooks app on slack 2. Enable trigger for `Merge request` 3. Create an MR, you will get notification 4. Update title / description of the MR, you won't get any notification on slack 5. Approve/Removing of approvals works fine ### Example Project (If possible, please create an example project here on GitLab.com that exhibits the problematic behavior, and link to it here in the bug report) (If you are using an older version of GitLab, this will also determine whether the bug is fixed in a more recent version) ### What is the current *bug* behavior? No notifications on slack for changes in MR title/description. ### What is the expected *correct* behavior? Notification on slack for any changes in title or description ### Relevant logs and/or screenshots (Paste any relevant logs - please use code blocks (```) to format console output, logs, and code as it's tough to read otherwise.) ### Output of checks This bug happens on self hosted gitlab v12.10.3-ee #### Results of GitLab environment info <details> <summary>Expand for output related to GitLab environment info</summary> <pre> Don't have admin privileges to run this </pre> </details> #### Results of GitLab application Check <details> <summary>Expand for output related to the GitLab application check</summary> <pre> Don't have admin privileges to run this command </pre> </details> ### Possible fixes (If you can, link to the line of code that might be responsible for the problem)
issue