Project

General

Profile

Bug #12829

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

Added by François ARMAND 11 months ago. Updated 7 months ago.

Status:
Released
Priority:
N/A
Category:
Web - UI & UX
Target version:
Severity:
Major - prevents use of part of Rudder | no simple workaround
User visibility:
Getting started - demo | first install | level 1 Techniques
Effort required:
Very Small
Priority:
93

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

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

Related issues

Related to Rudder - Bug #10660: We have no way to know that a Technique is disabledReleasedActions
Related to Rudder - User story #12838: Allows to enable/disable technique from directive pageNewActions

Associated revisions

Revision e75b27d1 (diff)
Added by Raphael GAUTHIER 7 months ago

Fixes #12829: We have no way to know that a Technique is disabled

History

#1

Updated by François ARMAND 11 months ago

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

Updated by François ARMAND 11 months 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...

#3

Updated by François ARMAND 11 months ago

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

Updated by Raphael GAUTHIER 11 months ago

  • Status changed from New to In progress
#7

Updated by Vincent MEMBRÉ 10 months ago

  • Target version changed from 4.3.3 to 4.3.4
#8

Updated by Benoît PECCATTE 10 months ago

  • Target version changed from 4.3.4 to 4.3.5
#9

Updated by François ARMAND 8 months ago

  • Priority changed from 98 to 95
#10

Updated by Vincent MEMBRÉ 7 months ago

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

Updated by Raphael GAUTHIER 7 months 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
#12

Updated by Rudder Quality Assistant 7 months ago

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

Updated by Raphael GAUTHIER 7 months ago

  • Status changed from Pending technical review to Pending release
#14

Updated by Vincent MEMBRÉ 7 months 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
#15

Updated by Vincent MEMBRÉ 7 months 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
#16

Updated by Vincent MEMBRÉ 7 months 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

Also available in: Atom PDF