View Issue Details
ID | Project | Category | View Status | Date Submitted | Last Update |
---|---|---|---|---|---|
0010179 | mantisbt | public | 2009-03-03 14:32 | 2009-03-04 12:55 | |
Reporter | kvida | Assigned To | |||
Priority | normal | Severity | feature | Reproducibility | N/A |
Status | acknowledged | Resolution | open | ||
Platform | any | OS | any | OS Version | any |
Product Version | 1.1.6 | ||||
Summary | 0010179: Send mail notifications to project-related users only. | ||||
Description | Hello, after updating from 1.1.1 (where everything worked as wanted) to 1.1.6, the e-mail notification behaviour has changed. Changing the 'min_threshold' from NOBODY to ANYBODY in $g_default_notify_flags in the configuration file improved this. I would therefore like to request the addition of a "ANYBODY_RELATED" or similar flag (and functionality) to Mantis, which is the subset of ANYBODY that is registered for the project for which the notification is being sent. Are there any good workarounds to this? In #mantishelp, nuclear_eclipse recommended making all projects private to achieve this effect. I will try that ASAP. Are there any other ways? Thanks a lot for your time! | ||||
Tags | No tags attached. | ||||
Reminder sent to: giallu, grangeway Gianluca/Paul: can you take a look at this for me? I think that it should be as "simple" as adding a new flag for project members, but I don't know enough about how the notification system works... Cheers |
|
to the reporter. Are you sure this was working as expected before the upgrade? as John implies, we currently miss code for doing what you request... On the other side, if the behaviour of your Mantis installation changed (whatever it was before ;) ) maybe you did customize the config_defaults_inc.php file instead of config_inc.php? |
|
Hello John, Hello Gian-Luca, thank you for looking into this matter so quickly. Gian-Luca: yes, since nobody complained back then about getting too many or not enough notifications. ;) Unfortunately I did not set up the previous version. That behaviour in 1.1.1 was (again, according to nuclear_eclipse) seen as a bug and adressed in 1.1.2 or 1.1.3. I just diff-ed the config-files, there is no customization. The only difference is my change (NOBODY->ANYBODY) that I mentioned in the description above. There were also no in-code customizations. |
|