Details
-
Type:
Improvement
-
Status: Closed (View Workflow)
-
Priority:
Major
-
Resolution: Fixed
-
Component/s: email-ext-plugin
-
Labels:None
-
Similar Issues:
Description
There should be a way to configure post-build email notifications such that if the same email address comes up more than once, the recipient won't receive multiple identical emails.
Example: If 'user@domain.com' is added in the recipient list for a trigger and they are also determined to be one of the committers/culprits, it should be possible to ensure that only 1 email is sent to 'user@domain.com'.
Attachments
Activity
It was already discussed somewhere? I can't find it. But as i see it - the whole point of multiple triggers is to trigger for multiple events and it doesn't refer to e-mails count at all.
But in most cases triggers produce exactly the same e-mails (however it is just default) and there is no reason to send several same e-mails for the same person. With current UI it's not easy to make e-mails unique across triggers.
Robert Cody
added a comment - It was already discussed somewhere? I can't find it. But as i see it - the whole point of multiple triggers is to trigger for multiple events and it doesn't refer to e-mails count at all.
But in most cases triggers produce exactly the same e-mails (however it is just default) and there is no reason to send several same e-mails for the same person. With current UI it's not easy to make e-mails unique across triggers. The triggers each allow you to specify a list of people to send to, a different subject, a different body, even different attachment settings, so how is it hard to create a unique email per trigger?
Yes, that's my point - all trigger e-mails can be customized, so in current UI there is no clear way to resolve the problem. The problem is - there are many triggers and different subscribers, but some subscribers specified in several triggers and all triggers use base template (empty body, subject etc.), so if several triggers run in same time, user will receive several duplicate e-mails. And in current UI there is no way to prevent it.
The good way to fix this is - if trigger doesn't override any field (so it generates completely same e-mail as another trigger), then there should be only 1 such e-mail for specific subscriber. In more general case - we need to collapse generated e-mails by hash(body/subject/etc.) and then make recipient list unique by passing it in set.
Robert Cody
added a comment - Yes, that's my point - all trigger e-mails can be customized, so in current UI there is no clear way to resolve the problem. The problem is - there are many triggers and different subscribers, but some subscribers specified in several triggers and all triggers use base template (empty body, subject etc.), so if several triggers run in same time, user will receive several duplicate e-mails. And in current UI there is no way to prevent it.
The good way to fix this is - if trigger doesn't override any field (so it generates completely same e-mail as another trigger), then there should be only 1 such e-mail for specific subscriber. In more general case - we need to collapse generated e-mails by hash(body/subject/etc.) and then make recipient list unique by passing it in set. That might meet YOUR specific need, but the general usage of the plugin would suffer from the change. Each trigger is treated completely separately on purpose.
The whole point of multiple triggers is to send multiple emails.