[Patch] Never Notify Updater and Always Notify Component Owner flags

[sromanow@…]

Two things:

• Please add functionality of Never Notify Updater. Similar issue as #3778.
• Please add Always Update Component Owner flag so I can disable emails to this recipient class.

[Steve Romanow]

I like the thoughts on ​this ticket.

always* sure does get squishy when pressed.

I am concerned about if someone sets always_notify_updater and never_notify_updater. Since I am proposing carrying both options, it will be possible to set both on.

[Ryan J Ollos]

Replying to slestak:

I like the thoughts on ​this ticket.

I completely agree with that. From the testing I have done, it seems that the Never Notify updater plugin works with the Announcer plugin, but the never notify settings are over-ridden when Notify me of changes to tickets that I own and Notify me of changes to tickets that I reported are selected.

So, if Notify me of changes to tickets that I own and Notify me of changes to tickets that I reported are selected, and you are not the owner or the reporter, then you won't get an email notification for your own update. But if you are the owner or reporter, you will receive an email notifying you of your own update.

[Michael Ching]

Implementation of "nevernotifyupdater" for announcer legacy subscriber

[Michael Ching]

Attached file adds user-configurable option to prevent emails originating from a user's own updates if "never_notify_updater" is enabled in the [announcer] section of trac.ini.

[Ryan J Ollos]

Would it be possible to have this incorporated into the trunk?

[Ryan J Ollos]

Assigning to maintainer in case this one was missed.

[Robert Corsaro]

I've been thinking about this a lot. The trouble is that the rules can be complicated. One of my goals with the announcer plugin is to give the user more control over what notifications they receive. It is hard to make these complex rules accessible to the user, but here is where my mind is at now. The UI would look something like this and would be in the users preferences:

+alwaysnever notify me of changes to tickets that I own.
+alwaysnever+ notify me of changes to tickets that I created.
+neveralways notify me of changes to tickets that I modify.
etc..

The options would be setup to some default that makes sense for the site and the users would be able to do three things:

• disable/enable a rule
• select always/never for a rule
• change the order of the rules

The rules would be applied in order, so the ones lower in the list would always take precedence. The + would be some drag-n-drop thing. We could have something more simple for sans-javascript.

Does this make sense and seem like something people would want? Any better ideas?

[Ryan J Ollos]

Replying to doki_pen:

Seems like that would work well, provided you have the following rule.

+alwaysnever notify me of my own changes to tickets.

Would there be a way by which the administrator could specify a default set of rules?

[Ryan J Ollos]

One issue I have noticed with the current patch is that if I have "subscribed" to a ticket by adding myself to the CC list, the "Don't notify me of my own changes to tickets" is not respected.

[Robert Corsaro]

I tested on trunk and it works. If you add your username to the CC field, then things work as expected. There is no reverse lookup for email addresses, so you'll have to think of email addresses in CC fields as anonymous users with no settings (for now). Make a new ticket for reverse address lookup and I'll think about it some more, but it's unlikely to get done soon.

[Qudus]

Sorry for resurrecting this old ticket. I have googled a lot about this topic. And there doesn't seem to be a suitable solution so far.

The never_notify_updater option on the Announcer doesn't work. We're using Trac 1.0.8. never_notify_updater on Announcer is enabled and always_notify_updater on Notification is disabled. I have even added a user setting to never notify myself about my own changes.

But I am still getting useless emails bout my own changes.

Is this really a bug? Am I doing or understanding something wrong? Why doesn't this work after all these years? What wins? notification or announcer? Why are there both of them? We haven't installed any plugins.

The option to never notify myself about my own changes should always win over any other setting. May it be a global option or a user setting or a global default to a user setting.

[Ryan J Ollos]

Replying to Qudus:

We haven't installed any plugins.

Then you aren't using AnnouncerPlugin. If you are using Trac 1.0.x without any plugins, then you only need to be concerned with the notification section. You can try using NeverNotifyUpdaterPlugin to prevent notifications to self.

AnnouncerPlugin is being integrated to Trac for release 1.2, which should add the never notify self option (see ​trac:#2247)

[Qudus]

Thanks for the reply.

I am a bit confused. We just installed the latest Trac 1.0.8. There's no sign of 1.2.x. And according to the changelog the never_notify_updater thing was added with 1.0.3, though not functioning obviously.

The announcer brings the "never_notify_updater" option with it. I don't see "never_notify_self". This is really confusing, since on the internet there are a lot of articles, that tell about _self or _updater. I think, the Trac project should feature an FAQ about this topic, since it interests so many people and doesn'T seem to be easily configured, if even working.

When I last visited the NeverNotifyUpdaterPlugin's project page just a few days ago it said, that it was deprecated and replaced by Trac 1.0.3 core features. I don't see anything about this message now. All this is sooo confusing. We tried this plugin a year back and it didn't work. I will try it again.

Can you answer a question please? Why is this topic so complicated? Isn't it a simple and comprehencible request to never receive notifications about my own actions? I understand, that it might be a user option, but not a server wide option, which has been discussed here and there. But why doesn't the Trac project want this option to be available through core features and transparently and easily configuired?

[Ryan J Ollos]

Trac 1.0.x does not include never notify updater (self) functionality. For that you will need to use NeverNotifyUpdaterPlugin.

Trac 1.2 has not been released yet, but may include never notify updater (self) functionality, provided ​trac:#2247 is resolved by the time of the release.

Don't bother with AnnouncerPlugin. It's unmaintained and many features are broken.

[Qudus]

Yes, I know that ticket. Should be simple to elaborate a solution and fix this bug. If you're honest, it really isn't such a big deal.

Thanks for your time.

[Ryan J Ollos]

Feel free to provide a patch then.