View Issue Details
|ID||Project||Category||View Status||Date Submitted||Last Update|
|0021958||mantisbt||other||public||2016-11-26 18:50||2016-11-28 15:25|
|Priority||normal||Severity||minor||Reproducibility||have not tried|
|Summary||0021958: Developers on specific projects shouldn't be throttled|
The authors of the EmailReporting plugin have reported that they are being throttled by the anti-spam measures. It is likely that they are REPORTERs globally rather than DEVELOPERS. We should revisit this to only throttle users that are not DEVELOPERs on any project. We can also look at when should a user be considered white listed if they hit the default throttling policy.
|Tags||No tags attached.|
What kind of events should the antispam count?
In my experience i could add three notes before the antispam kicked in. After that i could still modify the status and assign issues
While if i modified a status including a note that currently is counted as 2 events. Meaning that if i resolved issues while including notes with the action i would reach the threshold faster and would be able to add less notes to issues then it the first example
Should the antispam evaluate a user on a project level or if a user has elevated rights in a single project should the antispam be ignored for all projects?