Bug 723373 - Bar graphs > 80% don't render correctly.
Summary: Bar graphs > 80% don't render correctly.
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Bugzilla
Classification: Community
Component: User Interface
Version: 3.6
Hardware: Unspecified
OS: Unspecified
unspecified
high vote
Target Milestone: ---
Assignee: Simon Green
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-07-20 01:41 UTC by Simon Green
Modified: 2014-10-12 22:46 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-07-28 23:52:38 UTC


Attachments (Terms of Use)
Example of incorrectly rendered graph (178.76 KB, image/png)
2011-07-20 01:41 UTC, Simon Green
no flags Details

Description Simon Green 2011-07-20 01:41:23 UTC
Created attachment 513904 [details]
Example of incorrectly rendered graph

Description of problem:
If a bar graph is > 80%, then the colored section does not render correctly.

Version-Release number of selected component (if applicable):
3.6

How reproducible:
Always

Steps to Reproduce:
1. Apply bug 587789 (should be in 3.6.5010)
2. Go Browse -> JBoss Enterprise SOA Platform 5 -> Roadmap
  
Actual results:
If you look at the attached screenshot, you can see that the bars for 100% are less than the bar for 93%, and the bar for 76% is just below 100%

Expected results:
The bar graph should accurately show percentages

Additional info:
The cause of this is that the graphs are rendered as a table 300 pixels wide, with two columns. If the width of the right column is not wide enough to show the text, the percentage in each column would not render correctly.

Comment 4 Simon Green 2011-07-21 08:36:31 UTC
Hi,

This change is now on partner-bugzilla.redhat.com, and is due to be released as part of today's upgrade on the live bugzilla server.

  -- simon

Comment 5 Simon Green 2011-07-28 23:52:38 UTC
Hello,

This change was released into production approximately 4 hours ago, as part
of Red Hat Bugzilla 3.6.5011.

  -- simon


Note You need to log in before you can comment on or make changes to this bug.