#0686 Idea - skipped notifications, delayed sending
One thing that bothers me personally when using the issuetracker is that I get lots of notifications about things that I've already noticed by being on the issue and letting it's AJAX features refresh the page so that I see when someone has replied to me.
What I'd like to achieve is the ability to not send notifications about followups to <insert user name> when <insert user name> already has a followup younger than the followup the notification is referring to.
This would be achieved by a cronjob that clears all unsent and un-attempted notifications and before sending a notification, there's a check for me recent followups.
This feature would not be on by default because cron jobs are always tricky but an "enterprise option" for those that use the issuetrackers a lot.
A potential issue... Expectations! If people are expecting to get an email, what would they think if non was received even if they wouldn't need the notification? Perhaps that's a risk to take.
Actually, this wouldn't just apply to followups but to new issues too. But for that, #0685 would first have to be completed.
5 months and 3 weeks and 5 days old
This has now been developed but is not checked in. I've written a unittest for it which passes. At the time of writing I haven't done a test for new issues notification and assignment notifications.
It's done! What this means now is that if you unset "Dispatch on submit" and point a cronjob to /dispatch people won't be notified on issues they've since participated in.
For more, see http://www.issuetrackerproduct.com/News/skipped-notifications