# GitLab webhook events on an MR do not notify MR assignee

**URL:** <https://forums.rocket.chat/t/gitlab-webhook-events-on-an-mr-do-not-notify-mr-assignee/20633>\
**Category:** Community Support\
**Created:** [September 23, 2024, 6:32pm UTC](https://forums.rocket.chat/t/gitlab-webhook-events-on-an-mr-do-not-notify-mr-assignee/20633 "2024-09-23T18:32:10Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![marcus-sigma](https://avatars.discourse-cdn.com/v4/letter/m/a9adbd/32.png) [@marcus-sigma](https://forums.rocket.chat/u/marcus-sigma)\
**Post date:** [September 23, 2024, 6:32pm UTC](https://forums.rocket.chat/t/gitlab-webhook-events-on-an-mr-do-not-notify-mr-assignee/20633/1 "2024-09-23T18:32:10Z")

</div>

### Description

I have a webhook set up in GitLab and an incoming integration set up in Rocket.Chat to post to a channel when someone comments on an MR. When I comment on an MR in GitLab, the person who made the last commit to the MR is always notified in the Rocket.Chat channel. Is there a way to make Rocket.Chat notify the assignee or assignees on the MR instead of or in addition to whoever made the last commit? Or is it possibly by design that only the person who made the last commit is notified?

This is on:

GitLab Enterprise Edition v17.2.5-ee  
RocketChat 6.2.10, free edition

### Server Setup Information

- Version of Rocket.Chat Server: 6.2.10, free edition
- Operating System:
- Deployment Method: 
- Number of Running Instances:
- DB Replicaset Oplog:
- NodeJS Version:
- MongoDB Version:
- Proxy: 
- Firewalls involved:

### Any additional Information

---

<div class="post-metadata">

**Author:** ![reetp](https://sea1.discourse-cdn.com/flex021/user_avatar/forums.rocket.chat/reetp/32/5546_2.png) [@reetp](https://forums.rocket.chat/u/reetp)\
**Post date:** [September 24, 2024, 8:21am UTC](https://forums.rocket.chat/t/gitlab-webhook-events-on-an-mr-do-not-notify-mr-assignee/20633/2 "2024-09-24T08:21:12Z")

</div>

> [@marcus-sigma](#):
>
> Version of Rocket.Chat Server: 6.2.10, free edition

Pretty sure you know this anyway. Upgrade to a supported version.

[https://docs.rocket.chat/docs/support-prerequisites](https://docs.rocket.chat/docs/support-prerequisites)

[https://docs.rocket.chat/docs/version-durability](https://docs.rocket.chat/docs/version-durability)

Beyond that I guess something is possible via your webhook scripts.

---

<div class="post-metadata">

**Author:** ![marcus-sigma](https://avatars.discourse-cdn.com/v4/letter/m/a9adbd/32.png) [@marcus-sigma](https://forums.rocket.chat/u/marcus-sigma)\
**Post date:** [September 24, 2024, 3:42pm UTC](https://forums.rocket.chat/t/gitlab-webhook-events-on-an-mr-do-not-notify-mr-assignee/20633/3 "2024-09-24T15:42:35Z")

</div>

@reetp Thank you for your reply. When you say I might be able to achieve this through webhook scripts, would those be on the GitLab side, or do you mean through altering the script in the Rocket.Chat documentation on this page: [GitLab](https://docs.rocket.chat/docs/gitlab#gitlab-rocketchat-integration)

---

<div class="post-metadata">

**Author:** ![reetp](https://sea1.discourse-cdn.com/flex021/user_avatar/forums.rocket.chat/reetp/32/5546_2.png) [@reetp](https://forums.rocket.chat/u/reetp)\
**Post date:** [September 24, 2024, 4:03pm UTC](https://forums.rocket.chat/t/gitlab-webhook-events-on-an-mr-do-not-notify-mr-assignee/20633/4 "2024-09-24T16:03:51Z")

</div>

Please don’t @ - it isn’t necesary.

People will help when they can.

I think you probably need to first look at what data Gitlab generates (nothing Rocket can do there) and then how Rocket oarses and displays it.

But first, upgrade.

And also tell me why you’ll pay for Gitlab, but not Rocket.Chat? Curious.