Project

General

Profile

Actions

bug #7048

closed

DB preferences allow override needs to be implemented per preference, not per preference page

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 it is only possible to set the flag per preference page. I haven't tested how this is semantically interpreted.


Files

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

Related issues

Related to EDIT - bug #7049: DB preferences should allow triple state to allow null values for checkboxesWorksformeKatja Luther

Actions
Actions #1

Updated by Andreas Müller over 5 years ago

  • Related to bug #7049: DB preferences should allow triple state to allow null values for checkboxes 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 Feedback
  • Target version changed from Unassigned CDM tickets to Release 5.37

I guess this is fixed in the meanwhile. Can you please double-check?

Actions #4

Updated by Andreas Müller over 1 year ago

  • Status changed from Feedback to Worksforme
  • Target version deleted (Release 5.37)

I checked again and it is definetely implemented in the meanwhile (at least for DB preferences). Close as worksforme.

Actions

Also available in: Atom PDF