Distinguish "mentions" from "subscribers"
Open, NormalPublic

Description

AFAICT, there is no way in which Phabricator or Gmail can tell me whether "I am being mentioned in a certain task" vs "I was already among the subscribers", right? Looks like other colleagues of mine would really appreciate being able to tell whether someone is actively calling for our attention, maybe even help, and hence having a certain priority, vs "this is the nth task I get just because I'm subscribed to a topic for which my interest may vary", which may or may not be read (my Phab folder has 18k unread messages and counting).

List of open tasks mentioned below:

List of closed tasks mentioned below, with relevant discussion points:

Elitre created this task.Nov 15 2016, 4:03 PM
Restricted Application added subscribers: TerraCodes, Aklapper. · View Herald TranscriptNov 15 2016, 4:03 PM
Aklapper triaged this task as "Normal" priority.
Restricted Application added a project: Upstream. · View Herald TranscriptNov 15 2016, 5:14 PM
Aklapper added a comment.EditedNov 15 2016, 5:48 PM

If you subscribe to a task you express that you are interested in receiving all updates about the task in order to closely follow its progress. So if you follow too many tasks you might want to decrease your interests a bit. :)

I can imagine that upstream maintainers would refuse this request to somehow "distinguish mentions from subscribers", as it might not be a "root problem" to solve.

When it comes to why this task was created, it looks like "too many notifications" is the underlying problem?

Maybe you want to be subscribed to less projects and tasks (or actively mass-unsubscribe from some), or fine-tune your mail notifications, or use web notifications for less important things and mail notifications for others.

@Elitre is currently subscribed to 1016 individual open tasks and a member of 33 projects. The latter means that by default you get notifications for all task changes associated to these projects if you have not explicitly clicked "Disable Mail". I am not sure if you really want that.

Related:

Related upstream tasks:

Even if I were following just 10 tasks, I'd still want the ability to tell whether I'm being pinged or the task is just part of the stuff I'm usually following, especially since both things can happen for a given task.

Thanks for listing them. https://secure.phabricator.com/T6297#88557 also feels relevant - a custom mail header could include an additional "User has been mentioned when this comment got added" value.

Aklapper added a comment.EditedNov 16 2016, 6:26 PM

Even if I were following just 10 tasks, I'd still want the ability to tell whether I'm being pinged or the task is just part of the stuff I'm usually following, especially since both things can happen for a given task.

As I kept wondering why you do not plan to follow (means: "read") notifications from tasks that you decided to follow, I realized: Am I correct that a higher urgency is implied (and hence faster attention required) when being explicitly mentioned in a comment, compared to a task you "just follow" by being subscribed?

Edit: Note to myself: Yes. That's what Erica already wrote in the task description but in other words, Andre.

Quiddity edited the task description. (Show Details)Nov 16 2016, 7:10 PM
Johan added a subscriber: Johan.Nov 21 2016, 2:40 PM

Use case: I write the technical newsletter for the Wikimedia wikis. This means I'm subscribed to a lot of tickets that would be difficult for me to unsubscribe from, because I'd miss when someone tells me "hey, this will go into production next week" or there's a relevant update. There's enough traffic that I miss some stuff, but I'd miss even more if I were subscribed to fewer tickets. If there was a custom mail header or at least anything, it'd help immensely.

(I've been able to mitigate most of this with various filters and other notifications, but the one thing that's really missing is something for being mentioned. There's no specific Phabricator setting for it and if you e.g. use Gmail (because you'd need to parse the entire email, which would be really slow in many clients but they do it anyway) the filter rule "Johan" is indistinguishable from the filter rule "@Johan". This is a problem in Gmail rather than in Phabricator, but if it had been solved in Phabricator there'd be need for a workaround from the very beginning.)