Increase granularity of email notification settings
Description
My team complained of too many GitLab emails. I tried various settings, but received either too many emails or not the right ones. We need a better option for what triggers email notifications.
Proposal
I came up with some options that might work, and am open to suggestions. I hope we can narrow it down to a specific change that solves the problem in most cases.
Option 1: Add a "person driven notification" option, where mentions (not just in comments!) and item assignment are what trigger emails, and little else. Good for small teams, used to direct communicating.
Option 2: A new notification level that's better attuned to what users want. Something like the current "participate" level but with some notifications removed. This requires discussion. This may be hard to settle on.
Option 3: Fine grained control. Checkboxes for every little thing (label, unlabel, assign, unassign, title change, description change, etc.). Can be set by users, owners, or system-wide by administrator.
Option 4: Other. I'm open to suggestions.
Documentation blurb
Docs for Option 1: Some teams have a problem with too many automated emails from GitLab, and would rather have notifications be driven by personal mentions and issue assignment. That's what this notification level does. Select it to only receive email notification when you're mentioned or assigned an issue.
Docs for Option 2: (contingent on final decision)
Docs for Option 3: (contingent on what the "fine grained options" are).
Docs for Option 4: (contingent on final decision)