Enhancement #27042
open
Node sorting by compliance doesn't differentiate between type of compliance
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 3 months 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)
Updated by Félix DALLIDET about 2 months ago
- Target version changed from 8.2.8 to 8.2.9
Updated by Clark ANDRIANASOLO 10 days ago
- Target version changed from 8.2.9 to 9.0.0~beta1
Clearly sub-order will be a mess to implement and maintain in Javascript, I couldn't find any relevant resource on subsorting with the Datatables library we use.
And we have already dealt (and known how to deal) with specific orderings and sub-orders in #26207 (plugins) and #27288 (security-benchmarks) in Elm.
This may need to wait for the nodes table being rescheduled for 9.1, there are many peculiar functionalities in that table that all need to be migrated in Elm.
Updated by Vincent MEMBRÉ 1 day ago
- Target version changed from 9.0.0~beta1 to 9.0.0~beta2