Bug 608011

Summary: 'Launcher Script' compatible group has two buttons of 'EDIT' & 'VIEW HISTORY' on connection page
Product: [Other] RHQ Project Reporter: Rajan Timaniya <rtimaniy>
Component: Core UIAssignee: John Mazzitelli <mazz>
Status: CLOSED WONTFIX QA Contact: Corey Welton <cwelton>
Severity: medium Docs Contact:
Priority: medium    
Version: 3.0.0CC: ccrouch
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-03-24 13:21:07 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 565628    
Attachments:
Description Flags
screenshot none

Description Rajan Timaniya 2010-06-25 12:04:44 UTC 
Created attachment 426864 [details]
screenshot

Description of problem:
'Launcher Script' compatible group has two buttons of 'EDIT' & 'VIEW HISTORY' on connection page.

Version-Release number of selected component (if applicable):
JON 2.4 GA_QA (tag-jon-release: 42)
http://hudson-qe.rhq.rdu.redhat.com:8080/view/JON/job/tag-jon-release/42/

How reproducible:
Always

Steps to Reproduce:
1) Log-in to JON server
2) Create compatible group for 'Launcher Script'
 	Click on 'INVENTORY' -> 'CONNECTION'
  
Actual results:
There isn't any property to modify but there are two buttons for 'EDIT' and 'VIEW HISTORY'.

Expected results:
There should be single copy of 'EDIT' and 'VIEW HISTORY' button, if there is any property to modify.

Additional info:
Please refer attached screenshot.
Comment 1 Joseph Marques 2010-09-28 15:43:00 UTC 
the reason this happens is because there is no config data for this type of resource.  however, instead of booting the user away from that tab to, say, summary>overview, we keep them there, and the user sees the buttons that would be at the top and the bottom of the table right next to each other.

solution: fix the resource type metadata so the config tab is invalid for this resource type.
Comment 2 John Mazzitelli 2010-09-30 13:49:31 UTC 
this is going to be addressed when we move away from JSF to GWT.

I think this issue can be closed as obsolete.
Comment 3 John Mazzitelli 2011-03-24 13:21:07 UTC 
this is no longer an issue because the GWT UI has separated the history view from the config editing view.