View Issue Details
ID | Project | Category | View Status | Date Submitted | Last Update |
---|---|---|---|---|---|
0017367 | mantisbt | custom fields | public | 2014-05-22 04:37 | 2017-04-17 09:55 |
Reporter | ujej | Assigned To | cproensa | ||
Priority | normal | Severity | minor | Reproducibility | always |
Status | closed | Resolution | fixed | ||
Product Version | 1.2.16 | ||||
Target Version | 1.3.4 | Fixed in Version | 1.3.4 | ||
Summary | 0017367: Custom Field - On The Manage Columns - Mantis changed value to lower case | ||||
Description | Manage Custom Field - If we had name of the field starting with Upper case, On View Issues We see column name for example @name@ and record value @name@ | ||||
Additional Information | I wrote about this here: | ||||
Tags | No tags attached. | ||||
MantisBT: master-1.3.x 414d19dd 2016-11-18 14:44 Committer: vboctor Details Diff |
Don't force lowercase for custom field column names Custom field names are referenced by name in columns definitions. There were some conversions in place to compare column names by converting to lowercase. However, the field name is stored in custom fields table without any conversion. This causes: - The configured columns array can be inconsistent with the available columns names. - When the database uses case sensitive matching, the columns are not shown properly and are presented as not existant. So given that custom field names are already stored with unrestricted names, which include spaces and non-alphanumeric characters, forcing them to lowercase while treating them is not a significant requirement at the moment. Fixes: 0017367, 0020248 |
Affected Issues 0017367, 0020248 |
|
mod - core/columns_api.php | Diff File | ||
MantisBT: master-2.2 c612d8da 2017-03-22 16:45 Committer: vboctor Details Diff |
Fix lowercase custom field column names Fix column names for custom field columns that may be stored as lowercase in configuration. See issue 0017367 If the system was working fine with lowercase names, then database is case-insensitive, eg: mysql. Fix by forcing a search with current name to get the id, then get the actual name by looking up this id. Fixes: 0022555 |
Affected Issues 0017367, 0022555, 0029413 |
|
mod - core/bug_api.php | Diff File | ||
mod - core/columns_api.php | Diff File | ||
mod - core/helper_api.php | Diff File |