Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.
Bug 1685266 - Service Dialog Date/DateTime Picker dynamic dialog values not displayed.
Summary: Service Dialog Date/DateTime Picker dynamic dialog values not displayed.
Keywords:
Status: POST
Alias: None
Product: Red Hat CloudForms Management Engine
Classification: Red Hat
Component: UI - OPS
Version: 5.10.1
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: GA
: 5.11.0
Assignee: drew uhlmann
QA Contact: Sudhir Mallamprabhakara
Red Hat CloudForms Documentation
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-03-04 20:07 UTC by William Fitzgerald
Modified: 2019-04-05 20:13 UTC (History)
8 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed:
Category: Bug
Cloudforms Team: CFME Core
Target Upstream Version:


Attachments (Terms of Use)
Date Picker and DateTime Picker not returning proper values (deleted)
2019-03-04 20:08 UTC, William Fitzgerald
no flags Details

Description William Fitzgerald 2019-03-04 20:07:03 UTC
Description of problem: Date Picker and DateTime Picker not returning proper values 


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

How reproducible:
100%

Steps to Reproduce:
1. Create a dialog with a Date Picker/DateTmie picker
2. Make the dialog field dynamic
3. Create a service and add your dialog
4. Order your service

Actual results:
Notice the date is tomorrow

Expected results:
Date should be today

Additional info:
Reproducer: 10.8.196.234
Order service vmware65_item1

Comment 2 William Fitzgerald 2019-03-04 20:08:15 UTC
Created attachment 1540719 [details]
Date Picker and DateTime Picker not returning proper values

Comment 4 drew uhlmann 2019-03-05 19:22:52 UTC
So I disagree with the premise of this ticket because it makes no sense to have a datetime picker that picks today, actually. That was initially set to tomorrow because in something like a retirement context, it makes no sense whatsoever to provision a vm that gets immediately retired. So the stated intended behavior of this please had better not be loading with today's date. That's just kinda idiotic. 

Actual results:
Notice the date is tomorrow

Expected results:
Date should be today
 
I hope not. Can I get someone to reevaluate that for me please? 

What I do think is wrong is that the date time picker and date picker, when dynamic, don't get the values set correctly by automate. But that's a far different thing than the stated reason this ticket was opened. 

I see the automate_values_hash method on the dialog running eight times for a single dynamic field, and that seems bad. 

Also this is pretty clearly a backend issue and probably shouldn't be assigned to Zita.

Comment 5 Loic Avenel 2019-03-05 20:31:34 UTC
it is a date Picker with Day + hours and minutes or just Day?

Comment 6 drew uhlmann 2019-03-05 20:37:07 UTC
The default, acting as designed behavior of _both_ types of fields, datetimepicker and datepicker, is for the default to be a day ahead of today.

Comment 7 drew uhlmann 2019-03-05 21:18:52 UTC
https://github.com/ManageIQ/manageiq/pull/18523


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