Project

General

Profile

Bug #10761

Screen estate in compliance graph

Added by Florian Heigl 7 months ago. Updated 29 days ago.

Status:
Released
Priority:
N/A
Category:
Web - UI & UX
Target version:
Target version (plugin):
Severity:
Minor - inconvenience | misleading | easy workaround
User visibility:
Getting started - demo | first install | level 1 Techniques
Effort required:
Medium
Priority:
31

Description

The SUM is above 100% in this screensho
your rounding is messed up
besides that - it assigns about 66% of screen estate to the missing / invalid / not OK regions
if it’s not even more
i don’t got a ruler here to check but the display is heavily biased towards errors
the reason is, there is just one “good” state, but at least 3 “bad” states, and the bad ones ALL eat into the good estate
it would be more sensible to first sum up the screen estate of all negative states and then calculate the spacing
i can’t imagine that the green area here is 44% of pixels.

Pasted image at 2017_05_20 12_06 AM.png (30.9 KB) Florian Heigl, 2017-05-20 00:14

Associated revisions

Revision 693963d7
Added by Raphaël Gauthier about 2 months ago

Fixes #10761: Screen estate in compliance graph

History

#1 Updated by François ARMAND 7 months ago

  • Subject changed from Screen estate AND rounding errors in compliance graph to Screen estate in compliance graph
  • User visibility changed from First impressions of Rudder to Getting started - demo | first install | level 1 Techniques
  • Priority changed from 0 to 35

We are splitting that one to take each part in a different ticket. #10773 will take care of the rounding error part, and this one will take care of the display estate between success and error.

Regarding that last part, the problem seems to occure due to the "zomm" feature which was added to better display very small percent. One idea would be to always put these zommed part at the end of the bar and provide a visual separator (circle around, slash, etc).

#2 Updated by Benoît PECCATTE 6 months ago

  • Priority changed from 35 to 50

#3 Updated by Raphael GAUTHIER 5 months ago

  • Effort required set to Medium
  • Priority changed from 50 to 33

#4 Updated by Raphael GAUTHIER 2 months ago

  • Target version set to 4.1.8
  • Priority changed from 33 to 32

#5 Updated by Raphael GAUTHIER 2 months ago

  • Status changed from New to In progress
  • Assignee set to Raphael GAUTHIER

#9 Updated by Raphael GAUTHIER about 2 months ago

  • Status changed from In progress to Pending technical review
  • Assignee changed from Raphael GAUTHIER to Vincent MEMBRÉ
  • Pull Request set to https://github.com/Normation/rudder/pull/1758

#10 Updated by Anonymous about 2 months ago

  • Status changed from Pending technical review to Pending release

#11 Updated by Vincent MEMBRÉ about 1 month ago

  • Status changed from Pending release to Released
  • Priority changed from 32 to 31

This bug has been fixed in Rudder 4.1.8 and 4.2.1 which were released today.

#12 Updated by Vincent MEMBRÉ 29 days ago

Raphaël, Can you provide a new screenshot of th ecompliance bar ?

Also available in: Atom PDF