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 almost 6 years ago. Updated over 5 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
 #1

Updated by François ARMAND almost 6 years ago

  • Related to Bug #10660: We have no way to know that a Technique is disabled added
Actions
Copy link
 #2

Updated by François ARMAND almost 6 years ago

It's major, because even if the workaround is trivial ounce you understand the problem, finding the problem is as hard as Nico+Far loosing a couple of cumulated hour on it. So I don't even know for a new user...

Actions
Copy link
 #3

Updated by François ARMAND almost 6 years ago

  • Related to User story #12838: Allows to enable/disable technique from directive page added
Actions
Copy link
 #4

Updated by Raphael GAUTHIER almost 6 years ago

  • Status changed from New to In progress
Actions
Copy link
 #7

Updated by Vincent MEMBRÉ almost 6 years ago

  • Target version changed from 4.3.3 to 4.3.4
Actions
Copy link
 #8

Updated by Benoît PECCATTE over 5 years ago

  • Target version changed from 4.3.4 to 4.3.5
Actions
Copy link
 #9

Updated by François ARMAND over 5 years ago

  • Priority changed from 98 to 95
Actions
Copy link
 #10

Updated by Vincent MEMBRÉ over 5 years ago

  • Target version changed from 4.3.5 to 4.3.6
  • Priority changed from 95 to 94
Actions
Copy link
 #11

Updated by Raphael GAUTHIER over 5 years ago

  • Status changed from In progress to Pending technical review
  • Assignee changed from Raphael GAUTHIER to Vincent MEMBRÉ
  • Pull Request set to https://github.com/Normation/rudder/pull/2053
Actions
Copy link
 #12

Updated by Rudder Quality Assistant over 5 years ago

  • Assignee changed from Vincent MEMBRÉ to Raphael GAUTHIER
  • Priority changed from 94 to 93
Actions
Copy link
 #13

Updated by Raphael GAUTHIER over 5 years ago

  • Status changed from Pending technical review to Pending release
Actions
Copy link
 #14

Updated by Vincent MEMBRÉ over 5 years ago

  • Subject changed from We have no way to know that a Technique is disabled to We have no way to know that a Technique is disabled when editing a Directive
Actions
Copy link
 #15

Updated by Vincent MEMBRÉ over 5 years ago

  • Subject changed from We have no way to know that a Technique is disabled when editing a Directive to We have no way to know that a Technique is disabled when editing a Directive
Actions
Copy link
 #16

Updated by Vincent MEMBRÉ over 5 years ago

  • Status changed from Pending release to Released
This bug has been fixed in Rudder 4.3.6 and 5.0.2 which were released today. 
Changelog
 Changelog
Actions
Copy link

Also available in: Atom PDF