Project

General

Profile

Bug #5714

Compliance percents are not sorted correctly

Added by Florian Heigl almost 6 years ago. Updated over 5 years ago.

Status:
Released
Priority:
N/A
Category:
Web - UI & UX
Target version:
Severity:
User visibility:
Effort required:
Priority:

Description

You can click on the compliance heading to sort descending or ascending by the compliance percentage.
But it has a nun-numerical sorter, so it doens't work.


Files

webapp_sorting.jpg (16.7 KB) webapp_sorting.jpg Florian Heigl, 2014-10-30 16:16

Related issues

Related to Rudder - Bug #2497: In the Configuration Management page, sorting on compliance % doesn't sort correctlyReleased2012-05-25Nicolas CHARLESActions
Has duplicate Rudder - Bug #4435: sorting compliance on rules is not validRejected2014-02-02Actions
Has duplicate Rudder - Bug #4773: The order of the sorted Rules are not logicalRejected2014-04-25Actions
Has duplicate Rudder - Bug #5281: When we sort by compliance, the ordering is not always correctRejected2014-07-21Actions
#1

Updated by Nicolas CHARLES almost 6 years ago

  • Description updated (diff)
  • Status changed from New to 8
  • Assignee set to Vincent MEMBRÉ
  • Target version set to 2.6.19

Thank you Florian for the bug report

This is something for our front end developer :)

#2

Updated by Vincent MEMBRÉ over 5 years ago

  • Target version changed from 2.6.19 to 2.6.20
#3

Updated by Vincent MEMBRÉ over 5 years ago

  • Status changed from 8 to Pending technical review
  • Assignee changed from Vincent MEMBRÉ to François ARMAND
  • Target version changed from 2.6.20 to 2.10.8
  • Pull Request set to https://github.com/Normation/rudder/pull/688
#4

Updated by Vincent MEMBRÉ over 5 years ago

  • Status changed from Pending technical review to Pending release
  • % Done changed from 0 to 100
#6

Updated by Vincent MEMBRÉ over 5 years ago

  • Subject changed from Webapp Sorting by compliance doesn't really handle numbers to Compliance percents are not sorted correctly
#7

Updated by Vincent MEMBRÉ over 5 years ago

  • Status changed from Pending release to Released

This bug has been fixed in Rudder 2.10.8 and 2.11.5, which were released today (16/12/14)

Also available in: Atom PDF