Bug 583669

Summary: Fail to input values in 'Scheduler Start Date' input control
Product: [Other] RHQ Project Reporter: Rajan Timaniya <rtimaniy>
Component: Core UIAssignee: Jay Shaughnessy <jshaughn>
Status: CLOSED DUPLICATE QA Contact: Corey Welton <cwelton>
Severity: medium Docs Contact:
Priority: low    
Version: 3.0.0CC: jsanda
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-19 14:31:08 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, 580175    
Attachments:
Description Flags
screenshot none

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 ***