View Issue Details
ID | Project | Category | View Status | Date Submitted | Last Update |
---|---|---|---|---|---|
0014820 | mantisbt | reports | public | 2012-10-12 05:24 | 2019-04-14 12:22 |
Reporter | JanHegewald | Assigned To | |||
Priority | normal | Severity | minor | Reproducibility | always |
Status | acknowledged | Resolution | open | ||
Product Version | 1.2.8 | ||||
Summary | 0014820: Summary Page graph 'By status' showing more than the statuses in the current workflow | ||||
Description | When choosing a specific project and then showing the Summary Page graph 'By status', all configured statuses (and not only those present in the workflow of the currently selected project) are taken into account for building the graphs. This is reproducible for every of the around 30 sub-projects I have. This might also apply to the other graphs 'By priority', 'By severity' and so on. | ||||
Additional Information | In my opinion this is caused by the usage of the function MantisEnum::getAssocArrayIndexedByValues in MantisGraph plugin file graph_api.php, which is not taking workflows and so on into account. | ||||
Tags | No tags attached. | ||||
Just had a look into master_1.2.x and master branch, the problem should be present there also. |
|
Here is what I did to resolve the problem (its more a workaround than a real solution): $t_assoc_array = MantisEnum::getAssocArrayIndexedByValues( $p_enum_string ); (line 584 in my installation) and foreach ( $t_assoc_array as $t_value => $t_label ) { in the file graph_api.php (function create_bug_enum_summary) of MantisGraph plugin. if(strcasecmp($p_enum,'status') == 0)
} |
|
in my case, it has also helped |
|