Actions
Bug #24882
closed
Bug #24501: Unexpected results when using compliance filters
Compliance doesn't show up at the top level in rudder 8.1.3~nightly
Status:
Released
Priority:
N/A
Assignee:
Category:
Web - Compliance & node report
Target version:
Pull Request:
Severity:
Minor - inconvenience | misleading | easy workaround
UX impact:
I hate Rudder for that
User visibility:
First impressions of Rudder
Effort required:
Very Small
Priority:
157
Name check:
To do
Fix check:
Checked
Regression:
No
Description
Top level is empty, we have to drill down to see it
Files
Updated by Nicolas CHARLES 7 months ago
- Severity set to Minor - inconvenience | misleading | easy workaround
- UX impact set to I hate Rudder for that
- User visibility set to First impressions of Rudder
- Effort required set to Very Small
- Priority changed from 0 to 157
Updated by Vincent MEMBRÉ 7 months ago
- Target version changed from 8.1.3 to 8.0.9
- Parent task set to #24501
Updated by Vincent MEMBRÉ 7 months ago
- Status changed from New to In progress
- Assignee set to Vincent MEMBRÉ
Updated by Vincent MEMBRÉ 7 months 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/5677
Updated by Anonymous 7 months ago
- Status changed from Pending technical review to Pending release
Applied in changeset rudder|893ad94f5a313d383101485cc74486f5ce47da27.
Updated by
Updated by Vincent MEMBRÉ 7 months ago
- Status changed from Pending release to Released
This bug has been fixed in Rudder 8.0.9 and 8.1.3 which were released today.
Actions