Bug 583669 - Fail to input values in 'Scheduler Start Date' input control
Summary: Fail to input values in 'Scheduler Start Date' input control
Keywords:
Status: CLOSED DUPLICATE of bug 562302
Alias: None
Product: RHQ Project
Classification: Other
Component: Core UI
Version: 3.0.0
Hardware: All
OS: Linux
low
medium
Target Milestone: ---
: ---
Assignee: Jay Shaughnessy
QA Contact: Corey Welton
URL:
Whiteboard:
Depends On:
Blocks: rhq_triage 580175
TreeView+ depends on / blocked
 
Reported: 2010-04-19 11:22 UTC by Rajan Timaniya
Modified: 2010-04-19 14:31 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2010-04-19 14:31:08 UTC
Embargoed:


Attachments (Terms of Use)
screenshot (80.67 KB, image/png)
2010-04-19 11:24 UTC, Rajan Timaniya
no flags Details

Description Rajan Timaniya 2010-04-19 11:22:54 UTC
Description of problem:
Fail to create schedule with start date, start date input control popup doesn't show date and also doesn't allow to enter start date manually.

Version-Release number of selected component (if applicable):
Verified on JON build #88 - Revision: 10607

How reproducible:
Always

Steps to Reproduce:
1) Log in to JON Server with appropriate credential
2) Create a reoccurring scheduled operation for some server in inventory with start date.
  
Actual results:
Fail to create schedule with start date, start date input control popup doesn't show date and also doesn't allow to enter start date manually.

Expected results:
Scheduler should create with start date, start date input control popup should show date and allow to pick the date from it.

Additional info:
Please refer attached screenshot

Comment 1 Rajan Timaniya 2010-04-19 11:24:01 UTC
Created attachment 407558 [details]
screenshot

Comment 2 John Sanda 2010-04-19 12:41:11 UTC
I actually came across this when working on bug 580175 and forgot to write up a bug report. I will take this since I am already familiar with the issue.

Comment 3 John Sanda 2010-04-19 13:39:23 UTC
Jay said that he checked in a fix for this last Friday. I am going to reassign to him since he already worked on it.

Comment 4 Jay Shaughnessy 2010-04-19 14:31:08 UTC

*** This bug has been marked as a duplicate of bug 562302 ***


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