Project

General

Profile

Bug #15101

Missing "disabled" status information in rules table

Added by François ARMAND 6 months ago. Updated 5 months ago.

Status:
Released
Priority:
N/A
Category:
Web - UI & UX
Target version:
Severity:
Minor - inconvenience | misleading | easy workaround
User visibility:
Operational - other Techniques | Rudder settings | Plugins
Effort required:
Priority:
65
Tags:

Description

We have two notion for rules status:

- 1/ is the rule enabled or disabled?
- 2/ is the rule applied or not applied?

A rule can be enabled but style not applied (because, for example, no group are defined).
Before Rudder 5.0, the status was in the "status" column (with an on mousover information of the cause of the status, for example "all directives are disabled"), and the rule own status was displayed next to the name when it was "disabled".
That last information isn't displayed anymore. We sometimes have a css rule after "- Unapplied", but it's redondant with the "status" column.


Files

Associated revisions

Revision ad7d64e3 (diff)
Added by Raphael GAUTHIER 6 months ago

Fixes #15101: the \"disabled\" label next to rule name isn't present anymore

History

#2

Updated by Raphael GAUTHIER 6 months ago

  • Status changed from New to In progress
#3

Updated by Raphael GAUTHIER 6 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/2279
#4

Updated by Raphael GAUTHIER 6 months ago

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

Updated by Alexis MOUSSET 5 months ago

  • Subject changed from the "disabled" label next to rule name isn't present anymore to The "disabled" label next to rule name isn't present anymore
#9

Updated by Nicolas CHARLES 5 months ago

  • Subject changed from The "disabled" label next to rule name isn't present anymore to Missing "disabled" status information in rules table
#10

Updated by Vincent MEMBRÉ 5 months ago

  • Status changed from Pending release to Released

This bug has been fixed in Rudder 5.0.12 which was released today.

Also available in: Atom PDF