View Issue Details

IDProjectCategoryView StatusLast Update
0020387mantisbtcustom fieldspublic2015-12-14 22:05
Reportervboctor Assigned To 
PrioritynormalSeverityminorReproducibilityhave not tried
Status newResolutionopen 
Product Version1.3.0-rc.1 
Summary0020387: Checkbox custom field is confusing

The way a checkbox is defined right now is as follows:

  • User selects name (e.g. Free Shipping)
  • User selects type (checkbox)
  • Possible Values -- it is confusing what that means to the user.
  • Default Value -- User would likely expect a bool here 0/1, true/false.

If user sets possible values to empty and default value to 0, that gets accepted, and later when they are reporting issues, they get invalid value for custom field error. Would be nice to be less confusion + do some validation at configuration time.

However, how it really works is as follows:

  • User has to select name (e.g. Free Shipping)
  • User selects type (checkbox)
  • Possible values - Enabled
  • Default value - empty for unchecked by default, or Enabled for checked by default.

We can also do more powerful scenarios:

  • Name - Shipping
  • Possible values: Gift|Fast Delivery
  • Default: empty or Gift or Fast Delivery or Gift|Fast Delivery

So from a feature set perspective, we seem to be OK, but the simple case is hard and confusing. If user





2015-12-14 22:05

manager   ~0052124

I also forgot to mention that if the user sets possible values and default value to empty. The checkbox will show up on the forms and will be ticked by default, but it won't persist the state in the mailbox (i.e. checked or not). It will always have an empty value in the database.

Issue History

Date Modified Username Field Change
2015-12-14 21:57 vboctor New Issue
2015-12-14 21:57 vboctor Tag Attached: mantishub
2015-12-14 22:05 vboctor Note Added: 0052124