View Issue Details
ID | Project | Category | View Status | Date Submitted | Last Update |
---|---|---|---|---|---|
0014356 | mantisbt | reports | public | 2012-06-06 02:23 | 2014-09-23 18:05 |
Reporter | linde_gao | Assigned To | dregad | ||
Priority | normal | Severity | minor | Reproducibility | always |
Status | closed | Resolution | fixed | ||
Product Version | 1.2.4 | ||||
Target Version | 1.2.12 | Fixed in Version | 1.2.12 | ||
Summary | 0014356: the statistics result in summary is wrong | ||||
Description | For Project XXX ,when click “Advanced Summary ”->” By Severrity”-> per Major defect has about 280. But when click “ Summary”->” Per severity ”-> per Major defect has about 230, the statistics result in summary is wrong. | ||||
Additional Information | Environment:
| ||||
Tags | No tags attached. | ||||
Attached Files | |||||
I am not able to reproduce the issue with latest stable version of MantisBT (1.2.10 at the moment) |
|
Thanks for your reply! |
|
Thanks for reporting your solution. I think your problem may be due to your custom status definition, linked with the related thresholds ($g_bug_resolved_status_threshold and $g_bug_closed_status_threshold), maybe you should check in your setup if everything is defined as it should. MantisBT makes the assumption that $g_bug_closed_status_threshold is the "final" status, i.e. the last one in the status enum. The graph plugin code you highlighted works fine in such standard setup, but will indeed fail to count some issues in the case a status code higher than $g_bug_closed_status_threshold exists, so there is indeed an issue with the code. That said, I believe your solution is incorrect as by definition there can be only 3 states for issues: open, resolved or closed. You are introducing a 4th state "Other" which does not really make sense in a global context (or is in any case not properly defined). I suggest you try the following patch, and let us know if that fixes your problem <pre>
|
|
Thank you very much for your explanation and Suggestions. I have used your patch and after test, data correct! |
|
Thanks atrol - used to be the source integration assigned automatically the fixed in version; apparently no longer the case with the last update jreese did. |
|
Marking as 'acknowledged' not resolved/closed to track that change gets ported to master-2.0.x branch |
|
MantisBT: master 7beac566 2012-06-14 20:47 Details Diff |
MantisGraph: incorrect issues count in graph by severity When $g_bug_closed_status_threshold is not the "final" entry in status_enum_string list, function enum_bug_group() in graph_api.php computed the number of closed issues incorrectly due to use of '=' operator instead of '>=' in the query's where clause. Also corrects some trailing whitespace. Fixes 0014356 |
Affected Issues 0014356 |
|
mod - plugins/MantisGraph/core/graph_api.php | Diff File | ||
MantisBT: master-1.2.x b63e1815 2012-06-14 20:47 Details Diff |
MantisGraph: incorrect issues count in graph by severity When $g_bug_closed_status_threshold is not the "final" entry in status_enum_string list, function enum_bug_group() in graph_api.php computed the number of closed issues incorrectly due to use of '=' operator instead of '>=' in the query's where clause. Also corrects some trailing whitespace. Fixes 0014356 |
Affected Issues 0014356 |
|
mod - plugins/MantisGraph/core/graph_api.php | Diff File | ||
MantisBT: master-2.0.x fbb5e95e 2013-04-06 03:29 Paul Richards Details Diff |
Port of 7beac566f25dc30ffb3224c2823fee77c9223a1b [dregad]: MantisGraph: incorrect issues count in graph by severity When $g_bug_closed_status_threshold is not the "final" entry in status_enum_string list, function enum_bug_group() in graph_api.php computed the number of closed issues incorrectly due to use of '=' operator instead of '>=' in the query's where clause. Also corrects some trailing whitespace. Fixes 0014356 |
Affected Issues 0014356 |
|
mod - plugins/MantisGraph/core/graph_api.php | Diff File |