Project

General

Profile

Actions
Copy link

Bug #5281

closed

When we sort by compliance, the ordering is not always correct

Bug #5281: When we sort by compliance, the ordering is not always correct

Added by Nicolas CHARLES about 12 years ago. Updated almost 12 years ago.

Status:
Rejected
Priority:
N/A
Assignee:
-
Category:
Web - Compliance & node report
Target version:
2.10.8
Pull Request:
Severity:
UX impact:
User visibility:
Effort required:
Priority:
Name check:
Fix check:
Regression:

Description

Sometimes, when we sort by compliance, we have a non logical order, like a lot of 100%, some 8x%, then some 9x%, and finally the N/A

Exists in 2.10.3, don't know if exists before or after

Related issues 3 (0 open — 3 closed)

Is duplicate of Rudder - Bug #5714: Compliance percents are not sorted correctlyReleasedFrançois ARMANDActions
Is duplicate of Rudder - Bug #4435: sorting compliance on rules is not validRejectedActions
Is duplicate of Rudder - Bug #4773: The order of the sorted Rules are not logicalRejectedActions

Updated by Nicolas PERRON about 12 years ago Actions
Copy link
 #1

  • Target version changed from 2.10.4 to 2.6.18

Updated by Nicolas PERRON about 12 years ago Actions
Copy link
 #2

  • Target version changed from 2.6.18 to 2.10.5

Updated by Vincent MEMBRÉ about 12 years ago Actions
Copy link
 #3

  • Target version changed from 2.10.5 to 2.10.6

Updated by Matthieu CERDA almost 12 years ago Actions
Copy link
 #4

  • Target version changed from 2.10.6 to 2.10.7

Updated by Vincent MEMBRÉ almost 12 years ago Actions
Copy link
 #5

  • Target version changed from 2.10.7 to 2.10.8

Updated by Jonathan CLARKE almost 12 years ago Actions
Copy link
 #6

  • Status changed from New to Rejected

This is a duplicate of #5714, #4435 and #4773. Please search for existing bugs before opening new ones!

Actions
Copy link

Also available in: PDF Atom