IssueTrackerProduct

A new feature has been added that helps avoid the annoying notifications that go out about issues you've already participated in.

This comes in very handy when you're using an issuetracker frequently and let the AJAX trick immediately let you know that a followup has been added. Let me try to explain...

1. Mr X adds an issue and assigns it upon creation to Mrs Y
2. This creates a notification to go out to Mrs Y about being assigned the issue
3. But coincidental luck Mrs Y notices the new issue by refreshing the home page and immediately clicks on the issue and takes the issue.
4. Now there's no point notifying Mrs Y about this new issue because clearly she's already seen it by actively participating in it.
5. The notification is therefore canceled

The above example is for issues being assigned to someone but the same applies to all kinds of notifications. Actually there are only three kinds: assignments, new issues and followups. So if you've ever found yourself bounching followups back and forth with someone almost like a chat and then an hour later you open your email program just to find lots of notifications about things you've already worked on that's a thing of the past.

Now, to set this up you need a cronjob that hits /dispatcher every now and then and this how-to will show you how it can be done: Setting up cron on Linux to send out delayed notifications

The issue where this was also discussed is Real#0686

UPDATE

And of course, one of the most important benefits of delayed notifications is that when you submit your issue or followup, the notification isn't sent as part of the request which can slow things down since it has to open a network connection to the mailserver.