MergeMe logoMergeMe
Published on

GitLab Slack Group Mentions: Fix Missing Notifications

Authors
  • Name
    Maruan

GitLab group mentions usually fail to appear in Slack because the group mention events are not ticked under the GitLab for Slack app's Trigger settings, no destination channel is set for them, or the @group_name was typed somewhere GitLab does not watch. Check those first, then test delivery in a restricted channel.

There is a second question behind the first. A message landing in a Slack channel is one thing. A Slack alert reaching a specific person is another, and the native app only controls the first. This guide walks through both so you can tell which one you are debugging.

It covers the native GitLab for Slack app on GitLab.com and self-managed. It does not cover individual user mapping, installation, or channel permissions in general.

Quick answer: why a GitLab group mention does not show up in Slack

A GitLab group mention does not show up in Slack when one of three things is off: the group mention event is not enabled, the event has no destination channel, or the mention was written in a place GitLab does not evaluate.

The flow is short. A group mention happens in GitLab, the configured native integration event matches it, and the app posts a message to the Slack channel you chose. If any link in that chain is missing, you get silence.

Use this decision list to find your link:

  • Nothing arrives at all: check the Trigger checkboxes and the destination channel first.

  • Other events arrive but mentions do not: the group mention checkbox is probably unticked, or the mention sits in an unsupported spot.

  • A message arrives but nobody got pinged: that is the channel-message versus person-alert distinction covered further down.

The group mention feature is generally available as of GitLab 17.8. On an older self-managed version, check its version-specific documentation before assuming the same settings are available.

Check the group mention events and the destination channel

Open the project, then go to Settings, Integrations, GitLab for Slack app, and look at the Trigger section. The relevant checkboxes are labelled Group mention in public and Group mention in private.

Tick the one you need, or both. Then give that event a Slack channel in the destination field next to it. An enabled event with an empty destination has nowhere to post, and a filled destination with an unticked event never fires. Both halves must be set.

A few practical checks:

  • Save the settings after changing them. It is easy to tick a box and navigate away.

  • Confirm the channel name is the one you are actually watching, not a similarly named channel.

  • If the destination is a private Slack channel, the app has to be a member. In that channel, mention @GitLab and choose Add to Channel.

  • Labels configured for the integration may limit which issues, merge requests, and comments are notified, so a missing label can look like a missing mention.

Don't assume the public or private wording maps neatly onto your project visibility or your Slack channel visibility. Treat the two checkboxes as the exact event names GitLab offers and enable the one that matches the situation you are testing. Don't route material you consider sensitive into a broadly visible channel just because an event is enabled.

If the integration is not working for any event, not just mentions, the failure is upstream of this guide. Start with GitLab Slack dispatch_failed: Checks for Self-Managed.

Mention the group where GitLab supports it

GitLab evaluates a group mention when you write @group_name, using the group's path, in an issue description, a merge request description, or a comment on an issue, merge request, or commit.

Those are the contexts listed in the current documentation. If your mention lives somewhere else, like a pipeline log, a wiki page, or a commit message body, don't expect an event.

Check these details:

  • Use the GitLab group's path exactly as GitLab renders it. A typo produces plain text, not a mention.

  • Type @group_name, not a Slack-style user group handle. GitLab groups and Slack user groups are separate systems with separate syntax.

  • Make sure the mention is in the description or comment you actually saved. A draft comment that was never posted fires nothing.

  • A mention inside a confidential issue deserves care. If confidential items are in play, read GitLab Slack confidential issues: Stop unwanted alerts before you enable the event on a shared channel.

A frequent mistake is mentioning the group in a place that feels natural, like a commit message, then wondering why the integration stayed quiet. Move the mention into a comment on the commit or merge request and try again.

A posted channel message is not a Slack alert for a person

The native app posts a message to a channel. Whether any individual human is notified depends on their own Slack notification preferences, and the app does not promise that every member of the GitLab group gets pinged.

Separate the two outcomes when you debug:

  • Channel message: did a message appear in the destination channel after the mention? If yes, the GitLab side is working.

  • Person alert: did a specific teammate get a Slack notification? That depends on their settings, whether they are in the channel, and how Slack treats the message.

If the message appears but a colleague says they heard nothing, the integration did its job. Next, check notification preferences, channel membership, and whether the message contains a resolved Slack mention. Slack's own user-group mechanics are a different subject again, and do not assume a GitLab group mention maps to a Slack user group. If you plan to rely on Slack user groups, check the current Slack documentation rather than assuming GitLab does it for you.

This also answers the common question of whether tagging someone in Slack notifies them. A mention in Slack can notify the person depending on their preferences, but a bot posting a message that includes text is not the same as Slack resolving a mention to a person.

If you need to alert an individual, inspect the actual Slack mention and that person's notification settings separately from the GitLab group event.

Test safely with a disposable issue or merge request

Test with a throwaway issue or merge request in a test project, posting to a restricted test channel, so no real conversation is disturbed and no sensitive content reaches Slack.

Run this sequence:

  • Create a test project and a private test Slack channel. Add the GitLab app to that channel with @GitLab and Add to Channel.

  • Set Group mention in public or Group mention in private, set the destination to the test channel, and save.

  • Open a disposable issue with non-sensitive text and write @group_name in the description.

  • Add a second test as a comment on that issue, then a third on a merge request, so you learn which contexts fire.

  • Record three things: whether a message arrived, which channel it went to, and separately whether a person received a Slack alert.

Writing down the three results separates configuration faults from preference faults. If the message arrives in the wrong channel, fix the destination. If it never arrives, go back to the checkboxes. If it arrives and a person is not alerted, look at their Slack settings.

Don't draw conclusions about delivery timing or internals from a single run. Repeat once to confirm, then clean up the disposable items.

For a broader test routine on merge request notifications, see GitLab Slack Label Filters: Match Rules and Safe Testing Steps.

If group mentions still fail after the steps above, the cause is usually a neighbouring setting rather than the mention itself.

Private channels are the first suspect. The app must be added to a private channel before it can post there, and a missing membership produces the same silence as an unticked event.

Labels come second. If you have restricted notifications by label, a mention on an item without the matching label won't appear. Temporarily clear the label restriction on your test project to rule it out.

Third, check whether you are expecting the wrong kind of event. Group mention events are separate from push, pipeline, and draft merge request notifications. If you expected commit alerts, read GitLab Slack push notifications: Fix missing commit alerts. If merge requests in draft state are the puzzle, see GitLab Draft Merge Request Slack Notifications: Alert When Ready.

Change one variable at a time. If you change the event, channel, and label all at once, you can't tell what fixed it.

Confirm the channel message first, then judge the person alert

Debug a missing GitLab group mention in order: event ticked, destination set, mention in a supported place, then check the channel before you check anyone's personal alerts. A controlled test helps distinguish those configuration issues from other delivery failures. If your team spends its review time in Slack and wants each GitHub pull request or GitLab merge request as one updating card, try MergeMe, which supports GitHub.com, GitLab.com, and self-hosted GitLab in one workspace, and start with the free Hobby plan.

FAQs

Why are GitLab group mentions not working in Slack?

Usually the Group mention in public or Group mention in private checkbox is unticked, the event has no destination channel, or @group_name was written outside an issue or merge request description or a comment on an issue, merge request, or commit. Check Settings, Integrations, GitLab for Slack app, Trigger, then save and retest.

Where do I enable GitLab group mention notifications for Slack?

Go to Settings, Integrations, GitLab for Slack app in your project, and find the Trigger section. Tick Group mention in public and/or Group mention in private, and set a Slack channel for the event. Save the settings. The feature is generally available from GitLab 17.8.

Does a GitLab group mention ping every member in Slack?

No promise of that. The native app posts a message to the configured channel. Whether an individual is alerted depends on their own Slack notification preferences and channel membership. Confirm the channel message arrived first, then check person-level settings separately.

How do I post GitLab group mentions to a private Slack channel?

Add the GitLab app to the private channel first: in that channel, mention @GitLab and choose Add to Channel. Then set that channel as the destination for the group mention event under the GitLab for Slack app Trigger settings and save.

Is a Slack user group the same as a GitLab group mention?

No. A GitLab group and a Slack user group are separate objects. Use @group_name in a documented GitLab context to test the GitLab event, then inspect the actual Slack message rather than assuming every member receives a resolved Slack mention.