View Issue Details
ID | Project | Category | View Status | Date Submitted | Last Update |
---|---|---|---|---|---|
0023260 | mantisbt | custom fields | public | 2017-08-23 18:16 | 2017-10-08 23:52 |
Reporter | cproensa | Assigned To | cproensa | ||
Priority | normal | Severity | minor | Reproducibility | have not tried |
Status | closed | Resolution | fixed | ||
Product Version | 2.6.0 | ||||
Target Version | 2.7.0 | Fixed in Version | 2.7.0 | ||
Summary | 0023260: Custom fields of type date are not sorted correctly | ||||
Description | The filter query does outer join with the custom field values table. When sorting, the result is ordered, eg: mysql: 3 < 2 < 1 The expected result for sorting is:
| ||||
Tags | No tags attached. | ||||
Is there any difference between 2) empty and 3) null for the end user? |
|
Currently, i think they are treated the same, for any custom field. See for example: 0003738:0017810 My concern is, should the empty values, when that field allows empty values to be entered, be ordered before the actual data? |
|
MantisBT: master dc68e440 2017-08-25 16:03 Committer: dregad Details Diff |
Fix sorting for number based custom fields For types numeric, float, and dates - Make nulls appear last in the ordered result. - Cast the values to sort them numerically. Fixes: 0023260, 0006872 |
Affected Issues 0006872, 0023260 |
|
mod - core/filter_api.php | Diff File |