Skip to content

GitLab Next

    • GitLab: the DevOps platform
    • Explore GitLab
    • Install GitLab
    • How GitLab compares
    • Get started
    • GitLab docs
    • GitLab Learn
  • Pricing
  • Talk to an expert
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
    • Menu
    Projects Groups Snippets
  • Get a free trial
  • Sign up
  • Login
  • Sign in / Register
  • GitLab FOSS GitLab FOSS
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 0
    • Issues 0
    • List
    • Boards
    • Service Desk
    • Milestones
    • Iterations
    • Requirements
  • Merge requests 0
    • Merge requests 0
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages & Registries
    • Packages & Registries
    • Package Registry
    • Container Registry
    • Infrastructure Registry
  • Monitor
    • Monitor
    • Metrics
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • Code review
    • Insights
    • Issue
    • Repository
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
Collapse sidebar

GitLab 15.0 is launching on May 22! This version brings many exciting improvements, but also removes deprecated features and introduces breaking changes that may impact your workflow. To see what is being deprecated and removed, please visit Breaking changes in 15.0 and Deprecations.

  • GitLab.org
  • GitLab FOSSGitLab FOSS
  • Issues
  • #42062
Closed (moved)
(moved)
Open
Created Jan 16, 2018 by Mario de la Ossa@mdelaossa💬Contributor

Add more notification reasons to the `X-GitLab-NotificationReason` email header (and email footer)

MR !16160 (merged) implements a way to signal to the user why they have received an email notification, but only implements own_activity, assigned, and mentioned reasons. The original issue (#41532 (closed)) has some more relevant discussion.

This issue is meant to encompass future work required in order to define all possible reasons for a user to be notified.

For example:

  • Label subscription
  • Watching the project, although not a participant in the topic of the email.
  • Participant (has commented in the past or is issue owner)
  • Subscriber

We could also consider having a separate reason for the owner of the issue/mr/etc

cc/ @smcgivern

Assignee
Assign to
Time tracking