Actions
Bug #24501
closed
Unexpected results when using compliance filters
Status:
Released
Priority:
N/A
Assignee:
Category:
Web - Compliance & node report
Target version:
Pull Request:
Severity:
Minor - inconvenience | misleading | easy workaround
UX impact:
It bothers me each time
User visibility:
First impressions of Rudder
Effort required:
Very Small
Priority:
118
Name check:
To do
Fix check:
Checked
Regression:
No
Description
If you select "Show only" and no status in a filter, the result is quite unexpected.
I am pretty sure that we do not want to filter anything if the user has not checked any status.
It currently remove the compliance bars but let every component displayed, which does not make any sense.
Files
Updated by Vincent MEMBRÉ 8 months ago
- Target version set to 8.0.9
- Priority changed from 121 to 120
Updated by Raphael GAUTHIER 8 months ago
- Status changed from New to In progress
- Assignee set to Raphael GAUTHIER
Updated by Raphael GAUTHIER 8 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/5642
Updated by Raphael GAUTHIER 7 months ago
- Status changed from Pending technical review to Pending release
- Priority changed from 120 to 119
Applied in changeset rudder|87935ae5f192ac289b98d597bec0d7ddb95cdb71.
Updated by Clark ANDRIANASOLO 7 months ago
- Fix check changed from To do to Checked
Updated by Vincent MEMBRÉ 7 months ago
- Status changed from Pending release to Released
- Priority changed from 119 to 118
This bug has been fixed in Rudder 8.0.9 and 8.1.3 which were released today.
Actions