View Issue Details
|ID||Project||Category||View Status||Date Submitted||Last Update|
|0022555||mantisbt||filters||public||2017-03-21 03:32||2017-04-01 00:13|
|Target Version||2.2.3||Fixed in Version||2.2.3|
|Summary||0022555: Regression in custom field sorting|
Due some recent change, the custom field sorting doesn't work in some cases. By doesn't work I mean that clicking on the custom field header on View Issues page has no effect. This didn't always happen, but after some investigations, I figured out that this happens in the case where a custom field is name "Some custom field" but references in View Issues columns list (from manage columns) as 'some custom field' (different case). The logic that shows the field is case insensitive, but the logic for sorting by the field is case sensitive.
If the custom field name in the Manage Columns configure is changed to use the correct case, the sorting works again.
Could this be introduced by 0017367 ?
|Tags||No tags attached.|
Seems to be the issue which is mentioned at 0022392:0055731
I have provided a fix in 0022392
however, i don't think it has to do with case sensitiveness... that may be another issue?
@cproensa I'm pretty sure there is a case sensitivity issue since I was able to reproduce it, can you please test before / after your fix, so see if this issue is also fixed.
right, this issue is different than 0022392
I think that a proper fix would be to use custom field numeric ids in the parameters name for sorting and filter forms fields, instead of names.
Sounds good as long it doesn't break filters serialized in cookies or saved to db.
The approach is: when loading the columns from configuration, sanitize those referencing custom fields so that the actual cf names are used in runtime
MantisBT: master-2.2 c612d8da
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.
|mod - core/bug_api.php||Diff File|
|mod - core/columns_api.php||Diff File|
|mod - core/helper_api.php||Diff File|
|2017-03-21 03:32||vboctor||New Issue|
|2017-03-21 03:32||vboctor||Status||new => assigned|
|2017-03-21 03:32||vboctor||Assigned To||=> cproensa|
|2017-03-21 03:50||atrol||Relationship added||related to 0022392|
|2017-03-21 03:51||atrol||Note Added: 0056137|
|2017-03-21 18:59||cproensa||Note Added: 0056149|
|2017-03-21 19:01||vboctor||Note Added: 0056150|
|2017-03-21 19:51||cproensa||Note Added: 0056151|
|2017-03-21 21:55||vboctor||Note Added: 0056154|
|2017-03-22 21:09||cproensa||Note Added: 0056167|
|2017-03-22 22:25||vboctor||Changeset attached||=> MantisBT master-2.2 c612d8da|
|2017-03-22 22:25||cproensa||Status||assigned => resolved|
|2017-03-22 22:25||cproensa||Resolution||open => fixed|
|2017-03-22 22:25||cproensa||Fixed in Version||=> 2.2.3|
|2017-03-22 23:18||vboctor||Target Version||2.3.0 => 2.2.3|
|2017-03-27 17:00||cproensa||Relationship added||related to 0022325|
|2017-04-01 00:13||vboctoradmin||Status||resolved => closed|