Notificaton system in Core Trac is completely broken

[SirLouen]

Notifications are being sent without control. No unsubscription options, no notifications for subscribed components on new tickets, as soon as you do any triaging action like changing a keyword, you are automatically subscribed, and you will be receiving updates in your email for every single change in such ticket… Some days I receive 20+ emails for tickets I'm not interested in.

Basically, the notifications purpose has been defeated. At this point I'm receiving so many emails that I can't separate the wheat from the chaff.

The only good thing is that when someone mentions you, the Slack bot sends you a private message, so at least I'm not missing anything personal.

Basically the only option we have is filtering wp-trac@lists.wordpress.org or tagging those emails as spam 🥵

Ideally, emails should be sent only in these scenarios.

1. On reply => if you are subscribed to the ticket or if you have opened the ticket (and maybe if you are the ticket owner).

2. On a new ticket => if you are subscribed to that component specifically:

According to these instructions in:
​https://make.wordpress.org/core/notifications/

How it works:
You’ll receive all comments to tickets matching your preferences. If a ticket’s milestone or component changes to one you are not subscribed to, you will receive that final notification but no further updates, unless you have specifically starred and are watching that ticket (view list of your favorites).
If a sub-component is added and you are already subscribed to its parent component, you’ll automatically be subscribed to the new sub-component.

Please take a minute to review this because it's disturbing.

Thanks 🙏

[dd32]

Yes. It's known that it's broken. It won't/can't be fixed.

I can't find the ticket right now, but somewhere on trac:

https://meta.trac.wordpress.org/query?status=!closed&component=Trac&summary=~notifications

Please create specific tickets for any specific thing that's not working, as general tickets like this one are impossible to resolve.

#314 probably applies to some of your ticket. #3594 probably applies to others.