Custom Notification Settings Ignored for Pipeline Events

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

Summary

Users who have their global notification level set to Custom that have deselected the Pipeline fails, Pipeline is fixed, and Pipeline is successful notification events for it are seeing that notification emails for these events are still sent.

Steps to reproduce

  1. Configure your GitLab.com user notification settings to align with what is described in the Summary section above.
  2. Create a project with a .gitlab-ci.yml file that is designed to have its pipeline fail.
  3. Observe that you will still receive a notification email for the Pipeline fails notification event.

Example Project

Reproduced in https://gitlab.com/tw-test-bed/fail-then-fix/fail-then-fix-ci/-/jobs/8535211121

What is the current bug behavior?

Notification emails are still sent for users who have disabled the Pipeline fails notification event when their global notification level is set to Custom.

What is the expected correct behavior?

That notification emails for failed pipelines are only sent if the Pipeline fails notification event is enabled when a user has their global notification level set to Custom.

Relevant logs and/or screenshots

Example of .gitlab-ci.yml that is designed to fail:

stages:
  - test

failing_job:
  stage: test
  script:
    - echo "This will fail"
    - exit 1  # Forces the job to fail

Notification settings:

notification-settings

Notification email:

notification-email

Output of checks

This bug happens on GitLab.com

Edited by 🤖 GitLab Bot 🤖