Project

General

Profile

Actions
Copy link

Bug #10761

closed

Screen estate in compliance graph

Added by Florian Heigl over 7 years ago. Updated about 7 years ago.

Status:
Released
Priority:
N/A
Assignee:
Vincent MEMBRÉ
Category:
Web - UI & UX
Target version:
4.1.8
Pull Request:
https://github.com/Normation/rudder/p...
Severity:
Minor - inconvenience | misleading | easy workaround
UX impact:
User visibility:
Getting started - demo | first install | level 1 Techniques
Effort required:
Medium
Priority:
31
Name check:
Fix check:
Regression:

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.

Files

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

Related issues 2 (0 open — 2 closed)

Related to Rudder - Bug #18912: White empty segment in compliance bar due to computation bugResolvedRaphael GAUTHIERActions
Related to Rudder - Bug #20553: Regression on displaying small percent in compliance barReleasedVincent MEMBRÉActions
Actions
Copy link
 #1

Updated by François ARMAND over 7 years 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).

Actions
Copy link
 #2

Updated by Benoît PECCATTE over 7 years ago

  • Priority changed from 35 to 50
Actions
Copy link
 #3

Updated by Raphael GAUTHIER over 7 years ago

  • Effort required set to Medium
  • Priority changed from 50 to 33
Actions
Copy link
 #4

Updated by Raphael GAUTHIER about 7 years ago

  • Target version set to 4.1.8
  • Priority changed from 33 to 32
Actions
Copy link
 #5

Updated by Raphael GAUTHIER about 7 years ago

  • Status changed from New to In progress
  • Assignee set to Raphael GAUTHIER
Actions
Copy link
 #9

Updated by Raphael GAUTHIER about 7 years 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
Actions
Copy link
 #10

Updated by Anonymous about 7 years ago

  • Status changed from Pending technical review to Pending release
Actions
Copy link
 #11

Updated by Vincent MEMBRÉ about 7 years 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.

Actions
Copy link
 #12

Updated by Vincent MEMBRÉ about 7 years ago

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

Actions
Copy link
 #13

Updated by François ARMAND almost 4 years ago

  • Related to Bug #18912: White empty segment in compliance bar due to computation bug added
Actions
Copy link
 #14

Updated by François ARMAND almost 3 years ago

  • Related to Bug #20553: Regression on displaying small percent in compliance bar added
Actions
Copy link

Also available in: Atom PDF