| Anonymous | Login | Signup for a new account | 2013-05-25 22:05 EDT | ![]() |
| Main | My View | View Issues | Change Log | Roadmap | Wiki | ManTweet | Repositories |
| View Issue Details [ Jump to Notes ] [ Wiki ] | [ Issue History ] [ Print ] | ||||||||||||
| ID | Project | Category | View Status | Date Submitted | Last Update | ||||||||
| 0012030 | mantisbt | public | 2010-06-10 07:49 | 2013-05-24 11:46 | |||||||||
| Reporter | TomR | ||||||||||||
| Assigned To | |||||||||||||
| Priority | normal | Severity | minor | Reproducibility | always | ||||||||
| Status | confirmed | Resolution | open | ||||||||||
| Platform | OS | OS Version | |||||||||||
| Product Version | 1.2.0 | ||||||||||||
| Target Version | Fixed in Version | ||||||||||||
| Summary | 0012030: Email notify flags do not always work | ||||||||||||
| Description | I do not want reporters to get notified for changes in relationships, nor for updated issues. So I put in config_inc.php: $g_notify_flags['updated'] = array( 'reporter' => OFF, 'handler' => OFF, 'monitor' => OFF, 'bugnotes' => OFF, 'explicit' => OFF, 'threshold_min' => DEVELOPER, 'threshold_max' => MANAGER); $g_notify_flags['relation']['reporter'] = OFF; Can anyone explain why this is not working? Emails are still being sent to reporters. | ||||||||||||
| Tags | No tags attached. | ||||||||||||
| Attached Files | |||||||||||||
Relationships |
||||||
|
||||||
Notes |
|
|
TomR (reporter) 2012-05-03 09:38 |
This somehow related to 0011703 and 0013178 |
|
atrol (developer) 2013-05-24 11:46 |
Some of my thoughts from http://www.mantisbt.org/forums/viewtopic.php?f=2&t=21333&p=52066#p52066 [^] Nearly any change on page bug_update_page.php triggers sending of an e-mail which can't be suppressed by user settings. There are options to suppress e-mail for all kind of status change and nearly all kind of actions you can trigger from page view.php (add notes, close, reopen, .....) Ok, there is at least one kind of action where you also can't suppress the e-mail: add a relationship There is also no way to suppress messages which are triggered by change of custom fields. Furthermore the e-mail notification options would have to be project specific for a clean solution (they are global atm) as custom fields are project sepcific. We would end up in a quite huge list of options if every kind of notification can individually be set to on or off. Having an option like "E-mail on updated" is no solution as end users would not understand which change of an issue is an update and which is not. Maybe a global override option for the user could serve as an interim solution, something like "Disable all e-mail notifications" Seems that the e-mail notification system needs a redesign. |
Issue History |
|||
| Date Modified | Username | Field | Change |
| 2010-06-10 07:49 | TomR | New Issue | |
| 2012-05-03 09:38 | TomR | Note Added: 0031747 | |
| 2012-05-03 17:15 | rombert | Relationship added | related to 0013178 |
| 2013-05-24 10:48 | atrol | Status | new => confirmed |
| 2013-05-24 11:46 | atrol | Note Added: 0036967 | |
| MantisBT 1.2.16dev master-1.2.x-8c2bd07 [^]
Copyright © 2000 - 2013 MantisBT Team
Time: 0.0668 seconds. memory usage: 2,785 KB |