View Issue Details
ID | Project | Category | View Status | Date Submitted | Last Update |
---|---|---|---|---|---|
0006565 | mantisbt | filters | public | 2006-01-06 06:05 | 2006-02-04 05:44 |
Reporter | siebrand | Assigned To | thraxisp | ||
Priority | normal | Severity | block | Reproducibility | always |
Status | closed | Resolution | fixed | ||
Product Version | 1.0.0rc4 | ||||
Fixed in Version | 1.0.0rc5 | ||||
Summary | 0006565: Filters on custom fields failing | ||||
Description | After updating from 1.0.0rc2 to 1.0.0rc4 filters on custom fields (list) that worked before no longer work. The result is always all open calls, even though the custom field requirement is displayed. Possibly related to the same problem as mentioned in 0006501. I have applied the fixes in there (view_all_set.php -> 1.57.4.1.2.1, core/filter_api.php -> 1.122.2.2.2.3.2.1), but that didn't fix the problem. | ||||
Additional Information |
| ||||
Tags | No tags attached. | ||||
Attached Files | |||||
Fixed in CVS. core/filter_api.php -> 1.122.2.2.2.3.2.4 |
|
I have applied this patch (and only this patch) to rc4 and redeployed from rc2. Filters on custom fields are still failing. |
|
Which type of custom field fails to filter? Are you using simple or advanced filters? Does the appropriate text appear in the filter status pane after you hit "Apply Filter"? |
|
I will attach screenshots of the filter and the custom field definition. As seen in the screenshot, only filtering on membership of the custom field 'Listmember' = 'Buglist Woodwing' is used. The rest of the filter is standard. I have other saved filters on the same field that give exactly the same output. Attachments:
|
|
I propose to add a relation with 0005460 (critical 1.0.0 issues) for this issue. |
|
Could you please retest this using 1.0.0rc5? I can no longer reproduce this in either that or CVS HEAD. |
|
It is gone in 1.0.0rc5. Thanks for fixing it. |
|