Bug 1731991

Summary: Submit button is disabled when DatePicker and TimePicker fields set as required in dialog
Product: Red Hat CloudForms Management Engine Reporter: Satoe Imaishi <simaishi>
Component: UI - OPSAssignee: Martin Hradil <mhradil>
Status: CLOSED ERRATA QA Contact: Niyaz Akhtar Ansari <nansari>
Severity: high Docs Contact: Red Hat CloudForms Documentation <cloudforms-docs>
Priority: unspecified    
Version: 5.10.7CC: bmidwood, dmetzger, hkataria, lavenel, mpovolny, obarenbo
Target Milestone: GAKeywords: ZStream
Target Release: 5.10.8   
Hardware: Unspecified   
OS: Unspecified   
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: 1728600 Environment:
Last Closed: 2019-08-13 08:35:41 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: CFME Core Target Upstream Version:
Bug Depends On: 1728600    
Bug Blocks:    

Comment 2 CFME Bot 2019-07-22 21:18:18 UTC
New commit detected on ManageIQ/ui-components/hammer:

commit 1d7732078b6fb3ee2b6ef72586529629a723f2a6
Author:     Harpreet Kataria <hkataria@redhat.com>
AuthorDate: Fri Jul 19 09:22:44 2019 -0400
Commit:     Harpreet Kataria <hkataria@redhat.com>
CommitDate: Fri Jul 19 09:22:44 2019 -0400

    Merge pull request #401 from himdel/datetimesubmit-bz1728600

    Dialog user - fix validation for date & date&time when field is required; clearing the fields

    (cherry picked from commit 28592b743fd4092f1c8b9d4df8e984ba85dc4197)


 src/dialog-user/components/dialog-user/dialogField.html | 60 +-
 src/dialog-user/components/dialog-user/dialogField.ts | 14 +
 src/dialog-user/services/dialogData.spec.ts | 5 +-
 src/dialog-user/services/dialogData.ts | 48 +-
 4 files changed, 84 insertions(+), 43 deletions(-)

Comment 4 Niyaz Akhtar Ansari 2019-07-31 09:23:23 UTC
Verified in Version

Comment 6 errata-xmlrpc 2019-08-13 08:35:41 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.