Notification toggle UI has ambiguous scope
Everyone can contribute. Help move this issue forward while earning points, leveling up and collecting rewards.
The notification toggle on issues/MRs allows users to explicitly subscribe to notifications or to mute notifications if they've already been subscribed explicitly or implicitly:
I have seen a user misunderstand this toggle, expecting that by turning it to the deactivated state they were turning off notifications for the MR for all users rather than just for themselves.
This might be related to gitlab-ce#49286 where the states of the toggle are discussed.
Current behavior?
The toggle is labelled "Notifications" without specifying that the scope is limited to the logged in user:
Notifications [ ]
Notifications [x]
Solution
The toggle should be phrased to make it clear that this is a personal subscription to notifications, e.g.:
Subscribe to notifications [for this issue/MR]
Stop getting notified [about this issue/MR] OR Unsubscribe from notifications [for this issue/MR]
This is maybe a bit verbose but perhaps there's a neater way to make the effect of the button clearer.
