Actions
Bug #24499
closed
Wrong error message when no result are found when using a compliance filter
Status:
Released
Priority:
N/A
Assignee:
Category:
Web - Nodes & inventories
Target version:
Pull Request:
Severity:
Trivial - no functional impact | cosmetic
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
The code of the filter has most likely been copy/pasted from the directive webpage since in the node page it also displays the following error when nothing is found:"No nodes match your filter.
The error message should be different in each page, on the node page it should say that no "rules" match the current filter.
Updated by Vincent MEMBRÉ 9 months ago
- Target version changed from 8.1.0~beta2 to 8.1.0~rc1
Updated by Elaad FURREEDAN 9 months ago
- Target version changed from 8.1.0~rc1 to 8.0.7
Updated by Elaad FURREEDAN 9 months ago
- Status changed from New to In progress
- Assignee set to Elaad FURREEDAN
Updated by Elaad FURREEDAN 9 months ago
- Status changed from In progress to New
- Target version changed from 8.0.7 to 8.1.0~rc1
Updated by Elaad FURREEDAN 9 months ago
- Target version changed from 8.1.0~rc1 to 8.0.7
Updated by Elaad FURREEDAN 9 months ago
- Status changed from In progress to Pending technical review
- Assignee changed from Elaad FURREEDAN to Vincent MEMBRÉ
- Pull Request set to https://github.com/Normation/rudder/pull/5525
Updated by Anonymous 9 months ago
- Status changed from Pending technical review to Pending release
Applied in changeset rudder|3ea2ae5adc451afd46b44737ea1bc1ec90f21a75.
Updated by Raphael GAUTHIER 9 months ago
- Fix check changed from To do to Checked
Updated by Vincent MEMBRÉ 9 months ago
- Status changed from Pending release to Released
This bug has been fixed in Rudder 8.0.7 which was released today.
Actions