Bug 818188 - Globally uncaught exception when using Resource group metric graph and no group is defined.
Summary: Globally uncaught exception when using Resource group metric graph and no gro...
Keywords:
Status: NEW
Alias: None
Product: RHQ Project
Classification: Other
Component: Alerts
Version: 4.4
Hardware: Unspecified
OS: Unspecified
medium
unspecified
Target Milestone: ---
: ---
Assignee: Nobody
QA Contact:
URL:
Whiteboard:
: 831129 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-05-02 12:10 UTC by Filip Brychta
Modified: 2022-03-31 04:27 UTC (History)
1 user (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed:
Embargoed:

Attachments (Terms of Use)
dashboard screenshot (35.18 KB, image/png)
2012-05-02 12:11 UTC, Filip Brychta 		no flags Details
portlet config screenshot (55.89 KB, image/png)
2012-05-02 12:11 UTC, Filip Brychta 		no flags Details
exception (1.87 KB, text/plain)
2012-05-02 12:12 UTC, Filip Brychta 		no flags Details
View All

Description Filip Brychta 2012-05-02 12:10:58 UTC 
Version-Release number of selected component (if applicable):
Version: 4.4.0-SNAPSHOT
Build Number: c5c7e25
GWT Version: 2.4.0
SmartGWT Version: 3.0


How reproducible:
Always

Steps to Reproduce:
1.create new custom dashboard with resource group metric graph (see customDashboard.png)
2. no metric is attached to this graph (see portletConfig.png)
3. click on portlet's refresh button (see customDashboard.png)
  
Actual results:
Globally uncaught exception

Expected results:
'No items to show' message

Additional info:
exception attached
Comment 1 Filip Brychta 2012-05-02 12:11:30 UTC 
Created attachment 581593 [details]
dashboard screenshot
Comment 2 Filip Brychta 2012-05-02 12:11:54 UTC 
Created attachment 581594 [details]
portlet config screenshot
Comment 3 Filip Brychta 2012-05-02 12:12:19 UTC 
Created attachment 581595 [details]
exception
Comment 4 Filip Brychta 2012-06-12 15:14:27 UTC 
*** Bug 831129 has been marked as a duplicate of this bug. ***
Note You need to log in before you can comment on or make changes to this bug.