Hi,

I'm testing bundled filter alerts in RC2. The problem that bundled filter alerts do not get sent appears to have been solved.

But now notifications are getting sent to those who should not receive them. Here's an example: Suppose I have set up three defects with the following field values:

DEFECT ID    DEFECT NAME    ASSIGNED TO      REPORTED BY
=========    ===========    ===========      ===========
1            Start fails    John Hunt        John Hunt
2            Window fails   John Hunt        Fred Blogs
3            Program fails  Fred Blogs       Fred Blogs

Suppose I then set up a bundled filter alert based on a filter that selects all defects having '%fails%' in Name, and which sends notifications to [ASSIGNED TO] and [REPORTED BY]. If I then multi-edit the Priority (or some other field) of these three defects, then a bundled notification containing ALL THREE DEFECTS gets sent to John Hunt, and such a bundled notification also gets sent to Fred Blogs. But John Hunt should not be notified regarding defect #3, since he is neither [ASSIGNED TO] nor [REPORTED BY] in this defect; and Fred Blogs should not be notified regarding defect #1, since he is neither [ASSIGNED TO] nor [REPORTED BY] in this defect.

This is currently the intended behavior,  the consolidated email is sent to all users on the list.  I can see the value in what you are saying, though.  I've added this as a request in our system.

---

Dan Suceava
http://www.axosoft.com

Hi Dan,

Thanks for your reply. One more point in favor of this approach is the fact that if the filter were set not to send consolidated emails, then John Hunt and Fred Blogs would each get only two emails, i.e. just for those defects in which they are entered. My expectation as an end-user would therefore be that, by activating the filter's "consolidation" feature, those two mails would get consolidated into one.