Project

General

Profile

Actions
Copy link

Bug #12829

closed

We have no way to know that a Technique is disabled when editing a Directive

Added by François ARMAND over 6 years ago. Updated about 6 years ago.

Status:
Released
Priority:
N/A
Assignee:
Raphael GAUTHIER
Category:
Web - UI & UX
Target version:
4.3.6
Pull Request:
https://github.com/Normation/rudder/p...
Severity:
Major - prevents use of part of Rudder | no simple workaround
UX impact:
User visibility:
Getting started - demo | first install | level 1 Techniques
Effort required:
Very Small
Priority:
93
Name check:
Fix check:
Regression:

Description

It seems that we broke #10660 again. This is extremelly frustrating and leads to lots of wasted time.

When a directive is disabled, we should ALSO tell it in the directive description, with the reason ("the directive is disable", "the technique is disabled").

Subtasks 1 (0 open — 1 closed)

Bug #13776: Fix compiling issue after "disabled Technique" display was upmerged in 5.0ReleasedVincent MEMBRÉActions

Related issues 2 (1 open — 1 closed)

Related to Rudder - Bug #10660: We have no way to know that a Technique is disabledReleasedFrançois ARMANDActions
Related to Rudder - User story #12838: Allows to enable/disable technique from directive pageNewRaphael GAUTHIERActions
Actions
Copy link

Also available in: Atom PDF