I'm currently on Gitlab Silver plan. Group level webhooks are not triggering on merge request actions when the project is nested within another group (i.e. is a grandchild rather than a child). If you have a structure like: ``` top-level nested-group my-nested-project my-top-level-project ``` Setting up a merge_request webhook for the `top-level` group it will be triggered by MR actions on `my-top-level-project`, but actions in `my-nested-project` won't trigger the webhook - to get these to work you need to setup the webhook in `nested-group` ### Steps to reproduce * Setup a group structure like top-level nested-group my-nested-project my-top-level-project * Create a webhook for the top level group on merge request events * Create a merge request in my-nested-project * Observe that the webhook is not invoked (check for a log in whatever service you handle the webhook - unfortunately there is not visibility of webhook invocations at a group level) * Create a merge request in my-top-level-project * Observe that the webhook is invoked ### What is the current *bug* behavior? Webhooks aren't triggered when the project is not the child of the group where webhooks are defined (e.g. the project is grandchild rather than children of the group) ### What is the expected *correct* behavior? Webhooks are triggered for all descendants of the group webhook