Bug 639315 - Monitoring-Schedules 'Set' and 'Refresh' buttons looks odd
Summary: Monitoring-Schedules 'Set' and 'Refresh' buttons looks odd
Alias: None
Product: RHQ Project
Classification: Other
Component: Core UI
Version: 4.0.0
Hardware: All
OS: Linux
medium vote
Target Milestone: ---
: ---
Assignee: Jay Shaughnessy
QA Contact: Corey Welton
Depends On:
Blocks: rhq4
TreeView+ depends on / blocked
Reported: 2010-10-01 12:32 UTC by Rajan Timaniya
Modified: 2011-05-24 01:07 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2011-05-24 01:07:47 UTC

Attachments (Terms of Use)
screenshot (175.01 KB, image/png)
2010-10-01 12:32 UTC, Rajan Timaniya
no flags Details
screenshot (152.90 KB, image/png)
2011-03-02 12:40 UTC, Venkat
no flags Details

Description Rajan Timaniya 2010-10-01 12:32:53 UTC
Created attachment 450996 [details]

Description of problem:
Monitoring-Schedules 'Set' and 'Refresh' buttons looks odd

Version-Release number of selected component (if applicable):
ci-rhq-master build #352

How reproducible:

Steps to Reproduce:
1) Install RHQ and agent 
2) Log-in to RHQ (ci-rhq-master build #352)  
3) Navigate resource(s)
4) Goto Monitoring-Schedules tab
5) Observe 'Set' and 'Refresh' buttons
Actual results:
Monitoring-Schedules 'Set' and 'Refresh' buttons looks odd

Expected results:
Monitoring-Schedules 'Set' and 'Refresh' buttons should be placed properly.

Additional info:
Please refer attached screenshot

Comment 1 Ian Springer 2011-02-15 17:18:04 UTC
I believe this is a dup of another issue that Mazz has fixed.

Comment 2 Venkat 2011-03-02 12:39:51 UTC
Replicated the steps which are given to reproduce, and now I'm able see the Set and Refresh buttons  properly.... 
Please find the attachments for the same 
with the following  build details...
Build#1056 (Version: 4.0.0-SNAPSHOT Build Number: 643ac4b)

Comment 3 Venkat 2011-03-02 12:40:51 UTC
Created attachment 481856 [details]

Comment 4 Corey Welton 2011-05-24 01:07:47 UTC
Bookkeeping - closing bug - fixed in recent release.

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