View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0010992 | mantisbt | filters | public | 2009-09-29 10:01 | 2012-09-16 17:21 |
| Reporter | bromberg | Assigned To | rombert | ||
| Priority | urgent | Severity | major | Reproducibility | always |
| Status | closed | Resolution | no change required | ||
| Product Version | 1.1.7 | ||||
| Summary | 0010992: Filter Bug with CustomFields | ||||
| Description | Hi, we've an Version 1.1.7 running. I've looked in the Tables and saw this: Customfield is "Multiselection list" with Values like: Other|CustomValue1|CustomValue2| Old value which is found by filter in Table is: |CUSTOMValue| Where is the Bug? Is there an workaround? | ||||
| Tags | No tags attached. | ||||
|
The Bug is in the file "filter_api.php". In previous versions -I'm not quite sure in which one was the change- customfields were surrounded with pipes (e.g. |CustomValue|). In the last version singlevalues were saved without any pipes. The filter function, however, is always looking for an entry with pipes. SOLUTION (for Mantis 1.1.8, original condition):
Old Line: New Line: |
|
|
Thanks, this solves the problem. But the Data in Database is with and without pipe... so the bug is at an other location... |
|
|
This works in MantisBT 1.2.x, so closing. |
|