bug #7049
DB preferences should allow triple state to allow null values for checkboxes
Status:
New
Priority:
Highest
Assignee:
Category:
taxeditor
Target version:
Start date:
11/02/2017
Due date:
% Done:
0%
Severity:
normal
Found in Version:
Description
Currently, if one changes a value e.g. a value on the specimen or observation page all the values are saved and set to either true or false, even if one only wants to define the behavior for 1 field.
A 3 state for the checkbox, if selected, should delete the according preference from the database.
Related issues
History
#1 Updated by Andreas Müller about 1 year ago
- Related to bug #7048: DB preferences allow override needs to be implemented per preference, not per preference page added
#2 Updated by Andreas Müller about 1 year ago
- Priority changed from New to Highest
