View Issue Details
ID | Project | Category | View Status | Date Submitted | Last Update |
---|---|---|---|---|---|
0007008 | mantisbt | filters | public | 2006-05-01 05:12 | 2007-12-21 23:16 |
Reporter | zend | Assigned To | vboctor | ||
Priority | normal | Severity | major | Reproducibility | always |
Status | closed | Resolution | fixed | ||
Target Version | 1.1.0 | Fixed in Version | 1.1.0a3 | ||
Summary | 0007008: "current project" in advanced filters always displays empty list | ||||
Description | When I select "Advanced filters" and set project filter as "current", the bug list is always empty. If I use current project's explicit name, it shows the list of bugs correctly. If I switch to "simple filters" the list is displayed correctly also. | ||||
Tags | No tags attached. | ||||
The version we are using is 1.1.0-CVS |
|
I suspect the bug is in filter_api.php near line 165 - where if ( 'advanced' == $t_view_type ) { is done. When "current" is used, project id is set to -3, and while previous if clause generated correct where clauses, this if would generate comparison of project ID to -3, which would always fail. This should be made else if for "if ( 'simple' == $t_view_type || in_array( META_FILTER_CURRENT, $t_filter['project_id'] ) ) {" clause, I think. |
|
In the case of simple filters, when a project is selected, all issues belong to this project and it's sub-projects are shown. In the case of advanced filters, if the "current" project is selected and it is the only one selected, then same behaviour as simple filters. Otherwise, in the case of advanced, if specific projects are selected, their sub-projects are not included. Note that selecting a project by it's specific name triggers the advanced logic, where selecting it via "current" can potentially trigger the simple filters logic if it is the only one selected. |
|