Filter Notifications by Change Type
Problem to solve
As a developer, I get too many Github notifications because my PM makes small adjustments to labels, milestones or weights, and I get notified of each change individually.
I think this is a particularly pernicious issue because it means every attempt to organize the issues (i.e. a good thing) creates a bunch of pointless email noise (i.e. a bad thing). Some people hate Gitlab notifications in our company because of this and just turn them all off.
This is made worse by the fact that the current "Custom" notification option seems to bear no relationship to the control it is customizing:
There is no obvious way to understand how I can replicate the global notifications levels with these detailed checkboxes. They seem to represent two entirely different models for dividing the notifications. When what I would expect to see on the "Custom" screen is whatever collection of checked boxes replicates the global level I had before customizing.
I'm guessing that 95% of the notifications I receive fall under "New Note", so this screen does nothing to help me customize my notifications, and actually creates more, not less noise, because participation no longer seems to matter.
Intended users
User experience goal
Only receive notifications that are relevant and don't create emails floods when someone tries to organize some tickets.
Proposal
The solution is to allow these notifications to be filtered by change type, so that I can filter out meaningless meta-data changes from actual comments that add new information to the issue.
Further details
The links at the bottom of the emails say you should go customize your notification settings and go read the docs, if you get too many notifications. This leads you here:
https://gitlab.com/help/user/profile/notifications
Which is a terrible piece of documentation that doesn't help me at all. The list of custom events on this page also doesn't match what is in the screenshot above.
Permissions and Security
No idea
Documentation
No idea
Availability & Testing
No idea
What does success look like, and how can we measure that?
People not hating Gitlab notifications with the burning passion of a thousand suns.
What is the type of buyer?
People who use their inboxes.
Is this a cross-stage feature?
No idea