Bug 602647 - Autogroup content page didn't have overall availability sign
Summary: Autogroup content page didn't have overall availability sign
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: RHQ Project
Classification: Other
Component: Core UI
Version: 3.0.0
Hardware: All
OS: Linux
low
medium
Target Milestone: ---
: ---
Assignee: RHQ Project Maintainer
QA Contact: Corey Welton
URL:
Whiteboard:
Depends On:
Blocks: rhq_triage
TreeView+ depends on / blocked
 
Reported: 2010-06-10 11:58 UTC by Rajan Timaniya
Modified: 2010-09-24 13:02 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2010-09-24 13:02:23 UTC
Embargoed:


Attachments (Terms of Use)
screenshot (159.33 KB, image/png)
2010-06-10 11:58 UTC, Rajan Timaniya
no flags Details

Description Rajan Timaniya 2010-06-10 11:58:22 UTC
Created attachment 422880 [details]
screenshot

Description of problem:
There isn't overall availability sign on the autogroup content page.

Version-Release number of selected component (if applicable):
JON 2.4 Beta1

How reproducible:
Always

Steps to Reproduce:
1) Log-in to JON server
2) Go to dashboard and click on any platform
3) Select any auto group (select 'JBossAS Server AutoGroup')
  
Actual results:
There isn't overall availability sign on the autogroup content page.

Expected results:
There should be overall availability sign on the autogroup content page.
1) When all the resources in the autogroup are available, the autogroup should no
overlay in autogroup content page.
2) If at least one of the resources in the autogroup is unavailable, the
autogroup should the red sign overlay in autogroup content page.
3) If at least one of the resources in the autogroup has unknown availability
state, the autogroup should a grey question mark overlay in autogroup content page.

Additional info:

Comment 1 Corey Welton 2010-09-24 13:02:23 UTC
closing per gwt effort


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