Bug 1075137

Summary: Patch Mgmt: "Rollback" button should be disabled, when "no items" are available in the table.
Product: [JBoss] JBoss Enterprise Application Platform 6 Reporter: Liz <lclayton>
Component: Web ConsoleAssignee: Harald Pehl <hpehl>
Status: CLOSED CURRENTRELEASE QA Contact: Jakub Cechacek <jcechace>
Severity: low Docs Contact: Russell Dickenson <rdickens>
Priority: unspecified    
Version: 6.3.0CC: brian.stansberry, crobson, hbraun, jkudrnac, lclayton, rhatlapa
Target Milestone: DR5   
Target Release: EAP 6.3.0   
Hardware: Unspecified   
OS: Mac OS   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-06-28 15:31:13 UTC Type: Bug
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: 1074493    
Bug Blocks:    

Description Liz 2014-03-11 14:48:08 UTC 
Description of problem:
When there are no file to rollback to, the "Rollback" button should be disabled. 

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


How reproducible:
100%

Steps to Reproduce:
1.Navigate to the Patch Mgmt page.
2.When the table is empty, select the "Rollback" button
3.

Actual results:
"Rollback" button is active and receives focus.

Expected results:
"Rollback" button should be disabled when there are no patches populating the table. 

Additional info:
Comment 1 Radim Hatlapatka 2014-03-21 13:40:54 UTC 
Verified with EAP 6.3.0.DR5
Comment 2 Liz 2014-05-13 15:24:25 UTC 
Other button state comments: 
- When the table is empty (or when the system is NOT in a "restart required" state), should the "Restart" button be disabled as well?
- It might be helpful to provide tooltips for the Patch table buttons("Apply a New Patch, Rollback, Restart"), to offer more guidance around when/how they are used.
Comment 3 Harald Pehl 2014-05-14 07:40:46 UTC 
In general changing button states depending on selection / state of a resource is hard to implement as it interfere with RBAC. That's the reason it is not done in the console in the current version. However I see the benefits behind it. I recommend to defer this feature to the next iteration.