Actions
Enhancement #27042
open
Node sorting by compliance doesn't differentiate between type of compliance
Status:
New
Priority:
2
Assignee:
Category:
Web - Compliance & node report
Target version:
Pull Request:
UX impact:
Suggestion strength:
User visibility:
Effort required:
Name check:
To do
Fix check:
To do
Regression:
No
Description
When we sort by compliance in node lists, non compliance are all treated the same: no reports, error, non compliance. So if we were to sort, for instance, to find nodes that are in no answer, the 100% non compliance will also show up mixed in the list.
So the idea would be to have a stricter sub-order for each main order, and error sub-order would be always something like error > non compliance > no reports (to be specified, not sure it's meaningfull here).
This is certainly a change, and specific to jstable. If the node table is rewritten in elm in 9.0, it can wait for that.
Updated by François ARMAND 22 days ago
- Tracker changed from Bug to Enhancement
- Description updated (diff)
- Assignee set to Clark ANDRIANASOLO
- Priority changed from To review to 2
- Priority deleted (
0)
Actions