Bug 1686038

Summary: Default Value for Dynamic Multi Select DropDown Behavior Inconsistent
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: medium    
Version: 5.9.5CC: bmidwood, bwoolf, dmetzger, hkataria, jprause, lavenel, mkanoor, mpovolny, nansari, obarenbo, tfitzger
Target Milestone: GAKeywords: ZStream
Target Release: 5.10.2   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: 5.10.2.1 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: 1669533 Environment:
Last Closed: 2019-04-02 07:46:16 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:
Embargoed:
Bug Depends On: 1669533    
Bug Blocks:    

Comment 2 CFME Bot 2019-03-06 15:22:00 UTC
New commit detected on ManageIQ/ui-components/hammer:

https://github.com/ManageIQ/ui-components/commit/c585afdc97af9c41f9ebe0e89c6e9936454d5850
commit c585afdc97af9c41f9ebe0e89c6e9936454d5850
Author:     Martin Povolny <mpovolny>
AuthorDate: Tue Mar  5 05:34:24 2019 -0500
Commit:     Martin Povolny <mpovolny>
CommitDate: Tue Mar  5 05:34:24 2019 -0500

    Merge pull request #365 from himdel/bz1669533

    dialogField - move logic for setting default_value to one place

    (cherry picked from commit 6fd0c7e4c60be863f790be97fca870d8738689e4)

    https://bugzilla.redhat.com/show_bug.cgi?id=1686038

 src/dialog-user/components/dialog-user/dialogField.html | 1 -
 src/dialog-user/components/dialog-user/dialogField.spec.ts | 30 +-
 src/dialog-user/components/dialog-user/dialogField.ts | 29 -
 src/dialog-user/services/dialogData.ts | 35 +-
 4 files changed, 40 insertions(+), 55 deletions(-)

Comment 10 errata-xmlrpc 2019-04-02 07:46:16 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.

https://access.redhat.com/errata/RHBA-2019:0694