Actions
Bug #13776
closedBug #12829: We have no way to know that a Technique is disabled when editing a Directive
Fix compiling issue after "disabled Technique" display was upmerged in 5.0
Pull Request:
Severity:
UX impact:
User visibility:
Effort required:
Priority:
0
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").
Updated by Vincent MEMBRÉ about 6 years ago
- Status changed from New to In progress
- Assignee set to Vincent MEMBRÉ
Updated by Vincent MEMBRÉ about 6 years ago
- Status changed from In progress to Pending technical review
- Assignee changed from Vincent MEMBRÉ to François ARMAND
- Pull Request set to https://github.com/Normation/rudder/pull/2054
Updated by Rudder Quality Assistant about 6 years ago
- Assignee changed from François ARMAND to Vincent MEMBRÉ
Updated by Vincent MEMBRÉ about 6 years ago
- Status changed from Pending technical review to Pending release
Applied in changeset rudder|d09953827786c81cf4f4520bc7ca43e992b5e248.
Updated by Vincent MEMBRÉ about 6 years ago
- Target version changed from 5.0.3 to 5.0.2
Updated by Vincent MEMBRÉ about 6 years ago
- Status changed from Pending release to Released
This bug has been fixed in Rudder 5.0.2 which was released today.
Changelog
Actions