<!--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> - [Work on this issue](https://contributors.gitlab.com/manage-issue?action=work&projectId=278964&issueIid=332743) - [Close this issue](https://contributors.gitlab.com/manage-issue?action=close&projectId=278964&issueIid=332743) </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 The Mattermost notifications configuration GUI (**Admin, Integrations, Mattermost notifications**) says, under the **Issue** checkbox, "Trigger event when an issue is created, updated, or closed.". However, only **new**, **close** and **reopen** events trigger a notification to Mattermost. Updates to the Issue title, description or any attributes such as due date, epic, assigned to etc. do not get notified. This behavior is different to that of webhooks, which do get triggered for updates, and it would seem logical if the Mattermost integration behaved in the same way. If a change to the Mattermost integration behavior can't be made, the documentation and GUI labels should be updated to reflect the true behavior. Similar behavior is seen with Merge Requests, which don't trigger a notification when updated or reverted - but they do when opened and merged. ### Steps to reproduce <!-- Describe how one can reproduce the issue - this is very important. Please use an ordered list. --> In GitLab version 13.12.1 1. Enable the Mattermost integration and enable the Issue trigger. 2. Create a new issue. 3. Notification message sent to Mattermost 4. Update the issue title, description, due date, assignee and epic. 5. **No notification sent to Mattermost**. 6. Close the issue. 7. Notification sent to Mattermost. ### What is the current *bug* behavior? <!-- Describe what actually happens. --> Updating an issue does not trigger a notification to Mattermost. ### What is the expected *correct* behavior? <!-- Describe what you should see instead. --> Updating an issue should trigger a notification to Mattermost. ### Possible fixes <!-- If you can, link to the line of code that might be responsible for the problem. -->