View Issue Details
|ID||Project||Category||View Status||Date Submitted||Last Update|
|0020387||mantisbt||custom fields||public||2015-12-14 21:57||2015-12-14 22:05|
|Priority||normal||Severity||minor||Reproducibility||have not tried|
|Summary||0020387: Checkbox custom field is confusing|
The way a checkbox is defined right now is as follows:
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:
We can also do more powerful scenarios:
So from a feature set perspective, we seem to be OK, but the simple case is hard and confusing. If user
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.