Mattermost integration - improvement

Everyone can contribute. Help move this issue forward while earning points, leveling up and collecting rewards.

• Close this issue

Problem

When using Mattermost for notification within Microsoft teams, the channel quickly gets overloaded.

Using Mattermost for notifications have great benefits for team members such as:

• Allow to see the new merge request
  • Track what is produced on the perimeter on which the developer works
• Allow to see the merge requests that have been merged
  • Be informed that working branches should be updated / rebased (locally or on remote)
• Allow to see the merge request closed / reopened
  • Be informed of changes abandoned or resumed

but it also means that all approvals and disapprovals are sent over the channel.

This results in an overflow of notifications for which users see no added value.

Moreover, these undesired events are not specified in the triggers

Proposal

Having more control over which notifications will be sent would allow each user to disable what they want to get notified by, avoid overflowing, which will make the integration more useful.