View Issue Details

WikiRelated ChangesetsJump to Notes
IDProjectCategoryView StatusDate SubmittedLast Update
0003973mantisbtbugtrackerpublic2004-06-26 14:322009-06-23 15:26
ReporterWandererAssigned Todhx  
PrioritynormalSeveritytweakReproducibilityalways
Status closedResolutionfixed 
PlatformAnyOSAnyOS VersionAny
Product Versiongit trunk 
Target Version1.2.0rc1Fixed in Version1.2.0rc1 
Summary0003973: "Reporter effectiveness" on summary calculated wrongly in case of using custom-severity attributes
Description

Any amount of custom severities can be added to Mantis installation easy, but summary_print_reporter_effectiveness() in summary_api operates with hardcoded severities-set AND multiplier values, thus - custom severities do nothing in calculation final weight

Steps To Reproduce

Check reporter effectiveness for any reporter, add issue with installation-specific severity, see identical "cost" of reporter in both cases

Additional Information

It can be easy solved in style of "dirty hack", but I think, collect all possible severities from config_inc (and user-defined multiplier from... confic_inc also???) will be better solution, which I can't write yet in a good manner

TagsNo tags attached.

Relationships

Relationship GraphDependency Graph
child of 0010330 closeddhx Remove all hardcoded enum levels from within Mantis code 

Activities

jreese

jreese

2009-06-12 14:27

reporter   ~0022118

Resolved as part of issue 0010330.
jreese

jreese

2009-06-13 09:51

reporter   ~0022150

Got click-happy over issue 0010330. =\
dhx

dhx

2009-06-20 13:55

reporter   ~0022211

Finally fixed now... I also cleaned up some of that UGLY summary_api code too in the process.

Related Changesets

MantisBT: master e877da17

2009-06-20 13:46

dhx


Details Diff		 Custom reporter effectiveness multipliers

Continuation of bug 10330 to remove hardcoded enum constants from the
Mantis codebase.

The summary reporter effectiveness statistics used to be generated by
using hardcoded multipliers for each different severity and resolution.
This posed a problem to anyone who defined their own custom severities
and resolutions, as there is no guarantee that the reporter
effectiveness would still remain a useful statistic.

This patch reintroduces the severity and resolution multipliers as user
customisable options in the Mantis configuration file. Users can now
correctly set the severity and resolution multipliers to custom values
and can define multipliers for custom severities and resolutions.		 Affected Issues
0003973
mod - core/summary_api.php Diff File
mod - config_defaults_inc.php Diff File
mod - docbook/adminguide/en/configuration.sgml Diff File