Project

General

Profile

Actions

User story #7616

closed

Overriden directives are not listed in reports information

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

Status:
Released
Priority:
3
Category:
Web - Compliance & node report
Target version:
UX impact:
Suggestion strength:
User visibility:
Effort required:
Name check:
Fix check:
Regression:

Description

On rule details -> compliance, we have the list of directive applied to the rule with for each directive, its own compliance and its components (with their compliance etc).

But if an unique directive is overriden by an other one, then THAT directive does not appear AT ALL in the list. Which is extremelly perturbing for an user.

We should shown them with a specific color, and some texte explaining that the directive is overriden by an other instance in some other rule.

See for context:
https://www.rudder-project.org/redmine/issues/5329#note-9


Files

shot-2018-05-16_00-05-22.jpg (48.9 KB) shot-2018-05-16_00-05-22.jpg François ARMAND, 2018-05-15 22:11

Subtasks 1 (0 open1 closed)

Bug #12660: JS error on node compliance details for rule with overiden directivesReleasedFrançois ARMANDActions

Related issues 4 (0 open4 closed)

Related to Rudder - Bug #5329: False "no answer" reporting when rules with "unique" directive are overriddenReleasedNicolas CHARLES2014-07-30Actions
Related to Rudder - User story #10326: 2 non-contradictory rules cause rule display to spinRejectedNicolas CHARLESActions
Related to Rudder - Bug #11917: No compliance from a Rule with only one Directive (from a technique created in the editor) when the Directive is also applied in another RuleReleasedVincent MEMBRÉActions
Related to Rudder - Bug #20383: Non system technique appears in "System status tab"ReleasedVincent MEMBRÉActions
Actions #1

Updated by François ARMAND about 9 years ago

  • Related to Bug #5329: False "no answer" reporting when rules with "unique" directive are overridden added
Actions #2

Updated by Vincent MEMBRÉ almost 9 years ago

  • Target version changed from 3.0.13 to 3.0.14
Actions #3

Updated by Vincent MEMBRÉ almost 9 years ago

  • Target version changed from 3.0.14 to 3.0.15
Actions #4

Updated by Vincent MEMBRÉ over 8 years ago

  • Target version changed from 3.0.15 to 3.0.16
Actions #5

Updated by Vincent MEMBRÉ over 8 years ago

  • Target version changed from 3.0.16 to 3.0.17
Actions #6

Updated by Vincent MEMBRÉ over 8 years ago

  • Target version changed from 3.0.17 to 2.11.23
Actions #7

Updated by Vincent MEMBRÉ over 8 years ago

  • Target version changed from 2.11.23 to 302
Actions #8

Updated by Alexis Mousset over 8 years ago

  • Target version changed from 302 to 3.1.12
Actions #9

Updated by Vincent MEMBRÉ over 8 years ago

  • Target version changed from 3.1.12 to 3.1.13
Actions #10

Updated by Vincent MEMBRÉ over 8 years ago

  • Target version changed from 3.1.13 to 3.1.14
Actions #11

Updated by Vincent MEMBRÉ about 8 years ago

  • Target version changed from 3.1.14 to 3.1.15
Actions #12

Updated by Vincent MEMBRÉ about 8 years ago

  • Target version changed from 3.1.15 to 3.1.16
Actions #13

Updated by Vincent MEMBRÉ about 8 years ago

  • Target version changed from 3.1.16 to 3.1.17
Actions #14

Updated by Vincent MEMBRÉ about 8 years ago

  • Target version changed from 3.1.17 to 3.1.18
Actions #15

Updated by Vincent MEMBRÉ almost 8 years ago

  • Target version changed from 3.1.18 to 3.1.19
Actions #16

Updated by Benoît PECCATTE almost 8 years ago

  • Tracker changed from Bug to User story
Actions #17

Updated by Vincent MEMBRÉ over 7 years ago

  • Target version changed from 3.1.19 to 3.1.20
Actions #18

Updated by Vincent MEMBRÉ over 7 years ago

  • Target version changed from 3.1.20 to 3.1.21
Actions #19

Updated by Vincent MEMBRÉ over 7 years ago

  • Target version changed from 3.1.21 to 3.1.22
Actions #20

Updated by Vincent MEMBRÉ over 7 years ago

  • Target version changed from 3.1.22 to 3.1.23
Actions #21

Updated by Vincent MEMBRÉ over 7 years ago

  • Target version changed from 3.1.23 to 3.1.24
Actions #22

Updated by Vincent MEMBRÉ about 7 years ago

  • Target version changed from 3.1.24 to 3.1.25
Actions #23

Updated by Benoît PECCATTE about 7 years ago

  • Target version changed from 3.1.25 to 4.1.9
Actions #24

Updated by Vincent MEMBRÉ about 7 years ago

  • Target version changed from 4.1.9 to 4.1.10
Actions #25

Updated by Benoît PECCATTE almost 7 years ago

  • Target version changed from 4.1.10 to Ideas (not version specific)
Actions #26

Updated by François ARMAND over 6 years ago

  • Assignee set to François ARMAND
Actions #27

Updated by François ARMAND over 6 years ago

  • Target version changed from Ideas (not version specific) to 4.1.12
Actions #28

Updated by François ARMAND over 6 years ago

  • Status changed from New to In progress
Actions #29

Updated by François ARMAND over 6 years ago

The proposed solution make overriden directives appear in the list, under there rules, with a policy mode "overriden" in orange. On mouse over, we get the overriding directive / rule :

Actions #30

Updated by François ARMAND over 6 years ago

  • Status changed from In progress to Pending technical review
  • Assignee changed from François ARMAND to Vincent MEMBRÉ
  • Pull Request set to https://github.com/Normation/rudder/pull/1931
Actions #31

Updated by Rudder Quality Assistant over 6 years ago

  • Assignee changed from Vincent MEMBRÉ to François ARMAND
Actions #32

Updated by François ARMAND over 6 years ago

  • Status changed from Pending technical review to Pending release
Actions #33

Updated by François ARMAND over 6 years ago

  • Subject changed from Overreriden directive are not listed in reports information to Overriden directives are not listed in reports information
Actions #34

Updated by Benoît PECCATTE over 6 years ago

  • Status changed from Pending release to Released

This bug has been fixed in Rudder 4.1.12, 4.2.6 and 4.3.1 which were released today.

Actions #35

Updated by Nicolas CHARLES over 6 years ago

  • Related to User story #10326: 2 non-contradictory rules cause rule display to spin added
Actions #36

Updated by François ARMAND about 6 years ago

  • Related to Bug #11917: No compliance from a Rule with only one Directive (from a technique created in the editor) when the Directive is also applied in another Rule added
Actions #37

Updated by Nicolas CHARLES about 3 years ago

  • Related to Bug #20383: Non system technique appears in "System status tab" added
Actions

Also available in: Atom PDF