Notification Rules for unread reports

[eleibr]

Proposal

At the moment the notifications for unread reports are sent to all recipients of a context, also if one of them as already read the report. Ex. Context with 3 recipients: A, B, C. If A has read the reports, notifications should not be sent to B and C because in this way these two recipients get spammed while the report has been already read by A.

Then, it would be better to configure this feature also on the sub-sites and not only on the main one, because it is intended to have sub-sites that may want to use different set up.

Motivation and context

• Reduce spam email notifications
• Grant possibility to configure this feature in different ways for single sub-sites

[evilaliv3]

Thank you @eleibr

In the processes developed so far users have always worked together requiring to get informed of any update and this causes the behaviour that you describe when not all the users are "active" on managing report or just not committed to work.

To implement what you suggest we should evaluate how to organize notifications dividing them in categories. e.g. new reports, updates, notification of expirations, status changes

Have you already evaluated a proper organization ? Do you have a proposal or would you be able to support this implementation?

[danielvaknine]

We agree with @eleibr , at least regarding the situation where A has handled it but B and C continues to receive notifications. Gets very spammy and many don't understand why they continue to get these emails

[danielvaknine]

Any progress on this? Sending this many emails may in the long term result in spam-labelling of emails on the recipient side.

Our experience is that recipients don't understand why they keep getting the same email over and over again when it's already being handled