0003973: "Reporter effectiveness" on summary calculated wrongly in case of using custom-severity attributes - MantisBT

Mantis Bug Tracker

View Issue Details [ Jump to Notes ] [ Wiki ] [ Related Changesets ]

[ Issue History ] [ Print ]

ID

Project

Category

View Status

Date Submitted

Last Update

0003973

mantisbt

bugtracker

public

2004-06-26 14:32

2009-06-23 15:26

Reporter

Wanderer

Assigned To

dhx

Priority

normal

Severity

tweak

Reproducibility

always

Status

closed

Resolution

fixed

Platform

Any

OS

Any

OS Version

Any

Product Version

git trunk

Target Version

1.2.0rc1

Fixed in Version

1.2.0rc1

Summary

0003973: "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

Tags

No tags attached.

Relationships

child of

closed

Remove all hardcoded enum levels from within Mantis code

Notes
(0022118) jreese (administrator) 2009-06-12 14:27	Resolved as part of issue 0010330.

(0022150) jreese (administrator) 2009-06-13 09:51	Got click-happy over issue 0010330. =\

(0022211) dhx (developer) 2009-06-20 13:55	Finally fixed now... I also cleaned up some of that UGLY summary_api code too in the process.

Related Changesets
MantisBT: master e877da17 Timestamp: 2009-06-20 17:46:38 Author: 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.
	mod - core/summary_api.php		[ Diff ] [ File ]
	mod - config_defaults_inc.php		[ Diff ] [ File ]
	mod - docbook/adminguide/en/configuration.sgml		[ Diff ] [ File ]

Issue History
Date Modified	Username	Field	Change
2004-06-26 14:32	Wanderer	New Issue
2004-06-28 00:59	sgrund	Issue Monitored: sgrund
2009-06-11 15:59	dhx	Relationship added	child of 0010330
2009-06-11 16:00	dhx	Status	new => assigned
2009-06-11 16:00	dhx	Assigned To	=> dhx
2009-06-12 14:27	jreese	Note Added: 0022118
2009-06-12 14:27	jreese	Status	assigned => resolved
2009-06-12 14:27	jreese	Resolution	open => fixed
2009-06-13 09:51	jreese	Note Added: 0022150
2009-06-13 09:51	jreese	Status	resolved => feedback
2009-06-13 09:51	jreese	Resolution	fixed => reopened
2009-06-20 13:54	dhx	Changeset attached	master e877da17 =>
2009-06-20 13:55	dhx	Note Added: 0022211
2009-06-20 13:55	dhx	Status	feedback => resolved
2009-06-20 13:55	dhx	Resolution	reopened => fixed
2009-06-20 13:55	dhx	Fixed in Version	=> 1.2.x
2009-06-20 13:55	dhx	Target Version	=> 1.2.x
2009-06-23 15:26	jreese	Status	resolved => closed

MantisBT 1.2.2 git master-1.2.x[^]

Copyright © 2000 - 2010 MantisBT Group

Time: 0.2440 seconds.
memory usage: 1,968 KB