View Issue Details
|ID||Project||Category||View Status||Date Submitted||Last Update|
|0021712||mantisbt||filters||public||2016-09-23 04:24||2017-02-01 22:47|
|Target Version||1.3.7||Fixed in Version|
|Summary||0021712: No way to filter "negative" for checkbox custom fields|
If you create a checkbox custom field, you can use the View Issues filtering to look for the "positive" value that indicates the checkbox is checked easily enough, but there's currently no way to look for the "negative" (not checked) value; setting the search criteria to '[none]' in 1.3.1 returns nothing.
This appears to be a side-effect of the change over to the use of the vertical bar delimiter around field values in mantis_custom_field_string_table: the checked value is stored in the form "|value|", but the unchecked value is stored as the null string (""). If you manually set the custom field default value to "||" (the delimited null string), MantisBT complains about invalid values when submitting an issue. Setting the database column default value appears to do nothing, it would seem that Mantis constructs an explicit 'value=""' when populating the database.
In 1.2.X, this functionality worked as I would expect; filtering for '[none]' returned the "field not checked" issues. In order to reinstate the functionality (we have a number of filters that relied on searching for "custom fields unchecked") I've had to kludge the unchecked values in the database into being "||".
|Tags||No tags attached.|
If I've put this in the wrong category, please correct.
Given a test DB with 3 issues (1, 2 and 3), a checkbox custom field with a single element labelled 'on', and a custom_field_strings table with the following values (note, no CF string defined for issue 1)
field_id bug_id value 1 2 <blank> 1 3 |on|
Applying the 3 distinct filters combinations returns the following results
It's worth noting that in both versions, the "unchecked" item is consistently stored as empty string in mantis_custom_field_string_table.value
Note: I set product version to 1.3.0-rc.2, although the issue probably existed before but can't easily be reproduced due to the bug with the collapse settings cookie (0020822)
|2016-09-23 04:24||PantsManUK||New Issue|
|2016-09-23 04:25||PantsManUK||Note Added: 0054066|
|2016-09-23 08:47||dregad||Status||new => confirmed|
|2016-09-23 08:47||dregad||Note Added: 0054068|
|2016-09-23 08:51||dregad||Product Version||1.3.1 => 1.3.0-rc.2|
|2016-09-23 08:51||dregad||Target Version||=> 1.3.2|
|2016-09-23 08:51||dregad||Note Added: 0054069|
|2016-10-02 19:16||dregad||Target Version||1.3.2 => 1.3.3|
|2016-10-30 23:23||vboctor||Target Version||1.3.3 => 1.3.4|
|2016-11-27 08:22||dregad||Target Version||1.3.4 => 1.3.5|
|2016-12-30 16:24||atrol||Target Version||1.3.5 => 1.3.6|
|2017-02-01 22:47||vboctor||Target Version||1.3.6 => 1.3.7|