Bug 568796

Summary: Usability issues in the Alert Condition creation UI
Product: [Other] RHQ Project Reporter: Jeff Weiss <jweiss>
Component: AlertsAssignee: Heiko W. Rupp <hrupp>
Status: CLOSED NOTABUG QA Contact: Corey Welton <cwelton>
Severity: medium Docs Contact:
Priority: low    
Version: 1.4CC: cwelton, dajohnso
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: 2010-04-21 20:38:46 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: 547833    

Description Jeff Weiss 2010-02-26 16:18:55 UTC 
Description of problem:
In the alert condition creation dialog, radio buttons would be better than select list for picking the type of condition.  There is plenty of screen real estate there to be able to see all the options without the need for an extra click to drop down a selectlist.

Also, on the "measurement baseline" dialog, the last select list should be on the same line as the textfield.  The textfield is actually way too big, it's supposed to be a percentage input, i can't imagine it being more than 5 characters.  Maybe make it 8 to be safe, but that's still way smaller than it is now.

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


How reproducible:


Steps to Reproduce:
1.
2.
3.
  
Actual results:


Expected results:


Additional info:
Comment 1 Justin Harris 2010-03-01 16:34:05 UTC 
Due to the JSF implementation of <h:inputSelectRadio>, this is not a trivial task to use radio buttons to select sections of a form.  Reading over the docs, this would take creating custom JSF components which is fairly involved.  If this is an important enough feature, maybe we want to file this as a separate bug?

The measurement dialog input size has been fixed in commit 15ff7e397d9a01af13937c7d806679918e2dda7d
Comment 2 Corey Welton 2010-03-23 18:21:02 UTC 
QA Verified part 2 of this bug.
Comment 3 Heiko W. Rupp 2010-04-21 19:54:09 UTC 
I think this issue is out-of-date with the rollback of this part of the UI to the old struts UI
Comment 4 Jeff Weiss 2010-04-21 20:38:46 UTC 
Yeah, this is fixed indirectly, or non reproducible or whichever.