View Issue Details
ID | Project | Category | View Status | Date Submitted | Last Update |
---|---|---|---|---|---|
0015761 | mantisbt | public | 2013-04-16 09:57 | 2022-12-24 04:59 | |
Reporter | philippkitzberger | Assigned To | |||
Priority | normal | Severity | minor | Reproducibility | always |
Status | acknowledged | Resolution | open | ||
Summary | 0015761: No email on status change with bugnote when user pref email_on_status = OFF | ||||
Description | When a user X has not set the email_on_status flag a status change doesn't result in an email to that user. I guess that's the intension behind this flag. In many cases a "status changer" also leaves a bugnote with the same update. Then no email is sent to user X regardless of the users setting for email_on_bugnote. Here's why. bug_update.php:
Line 226 adds the bugnote but doesn't send an email due to the 8th parameter being FALSE! Line 230 updates the bug itself. core/bug_api.php->update(...):
This calls: core/email_api.php->email_collect_recipients(...):
| ||||
Tags | No tags attached. | ||||
IMO this works as designed, because otherwise we would potentially send 2 notifications for the same event. All mails are sent at the end of the update() method. I guess you may have a point that no mail is sent in the case where we have status change + bugnote, because we consider that the status change event "overrides" (or includes) the bugnote event, or in other words that the note belongs to the status change. I can't think of a clean way of addressing this issue with the current notification model without potentially sending 2 emails. If you have an idea on how to fix that, a patch would be welcome. |
|