View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0014365 | MMW 5 | DB / Backup | public | 2017-08-28 14:29 | 2022-11-15 18:43 |
| Reporter | jiri | Assigned To | |||
| Priority | high | Severity | minor | Reproducibility | N/A |
| Status | closed | Resolution | fixed | ||
| Target Version | 5.0.1 | Fixed in Version | 5.0 | ||
| Summary | 0014365: Support more Custom fields | ||||
| Description | There have been request for >5 custom fields in the past. I think that we could increase the number to 10. Another issue is that sometimes numeric sorting is required. This could be solved by giving an option to configure how to sort each Custom field. Or, possibly better, to use the same collation we use for 'Track#' field, i.e. with a preference for numeric prefix of the sorted string ('11' is correctly sorted after '2' then). | ||||
| Tags | No tags attached. | ||||
| Fixed in build | 2116 | ||||
| related to | 0014972 | closed | michal | Added broader support for tag fields |
| related to | 0018904 | closed | Ludek | Numeric Sort incorrect in Custom Fields with non-numeric data |
| related to | 0019267 | feedback | zvezdan | SQL collation for natural sort order needed |
| related to | 0018111 | closed | Ludek | Custom fields numeric support |
