Project

General

Profile

Actions

bug #7049

closed

DB preferences should allow triple state to allow null values for checkboxes

Added by Andreas Müller over 5 years ago. Updated over 1 year ago.

Status:
Worksforme
Priority:
Highest
Assignee:
Category:
taxeditor
Target version:
-
Start date:
Due date:
% Done:

0%

Estimated time:
Severity:
normal
Found in Version:
Tags:

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.


Files

picture706-1.png (6.61 KB) picture706-1.png Andreas Müller, 11/02/2017 02:55 PM

Related issues

Related to EDIT - bug #7048: DB preferences allow override needs to be implemented per preference, not per preference pageWorksformeKatja Luther

Actions
Actions #1

Updated by Andreas Müller over 5 years ago

  • Related to bug #7048: DB preferences allow override needs to be implemented per preference, not per preference page added
Actions #2

Updated by Andreas Müller over 5 years ago

  • Priority changed from New to Highest
Actions #3

Updated by Andreas Müller over 1 year ago

  • Tags set to preferences
  • Status changed from New to Worksforme
  • Target version deleted (Unassigned CDM tickets)

This is implemented in the meanwhile. Please reopen if you think there is still something missing.

Actions

Also available in: Atom PDF