View Issue Details
ID | Project | Category | View Status | Date Submitted | Last Update |
---|---|---|---|---|---|
0006203 | mantisbt | filters | public | 2005-08-30 22:21 | 2005-08-31 23:04 |
Reporter | siberian | Assigned To | |||
Priority | normal | Severity | minor | Reproducibility | always |
Status | acknowledged | Resolution | open | ||
Product Version | 1.0.0rc1 | ||||
Summary | 0006203: If a custom filed's possible values is setted to "=versions", the field's filter won't work | ||||
Description | If a custom field's possible values is setted to "=function_name" format. | ||||
Tags | No tags attached. | ||||
Attached Files | |||||
I have done more test. I guess if a custom field's type is list or enum, its filter values are fetched form its "possible values". |
|
You are correct. Most of the filters do not provide meaningful values if they are project dependent and contain project specific values. My suggestion would be to select a specific project first. |
|
But filters for the default fields "product version" "Fixed in Version" work even if "All projects" are selected. |
|