Comment 12 for bug 330550

KIko,

Maybe in this case we don't have to communicate it to the user? If a reasonable thing happens by default, we don't have to warn about that. User indicated that the bug affects them; user receives email when the bug is closed. That's reasonable, and therefore we don't necessarily need to warn them it's going to happen. Only the unexpected needs to be warned about.

As for how they shut it up: the email they get could tell them how, at the bottom. Also: if they uncheck the affects-me box, then obviously that "subscription" goes away. And clicking Unsubscribe could either unsubscribe from all notifications, or drop down into a menu in which one can slide one's subscription from "none" to "all events", and the slider would already be on one of the low-traffic settings.

Er, I think all that may sound more complex than it is. The user isn't confronted with the complexity until they're actually trying to do something, at which point it confronts them with just the complexity needed to do what they want.

...although, the more I think about it, the more I wonder: what is our exact motivation for having the affects-me-too button in the first place?