Bug 1542722
Summary: | Service Dialogs: Default value for Radio button not rendered on the editing page | ||||||||
---|---|---|---|---|---|---|---|---|---|
Product: | Red Hat CloudForms Management Engine | Reporter: | Satoe Imaishi <simaishi> | ||||||
Component: | UI - OPS | Assignee: | eclarizi | ||||||
Status: | CLOSED DUPLICATE | QA Contact: | Antonin Pagac <apagac> | ||||||
Severity: | medium | Docs Contact: | |||||||
Priority: | high | ||||||||
Version: | 5.9.0 | CC: | brant.evans, cpelland, hkataria, lavenel, mpovolny, obarenbo, rblanco, smallamp | ||||||
Target Milestone: | GA | Keywords: | Regression | ||||||
Target Release: | 5.9.0 | ||||||||
Hardware: | Unspecified | ||||||||
OS: | Unspecified | ||||||||
Whiteboard: | |||||||||
Fixed In Version: | 5.9.0.20 | Doc Type: | If docs needed, set a value | ||||||
Doc Text: | Story Points: | --- | |||||||
Clone Of: | 1541988 | Environment: | |||||||
Last Closed: | 2018-02-13 17:24:15 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: | 1519405, 1541988 | ||||||||
Bug Blocks: | |||||||||
Attachments: |
|
Comment 3
Satoe Imaishi
2018-02-06 22:01:57 UTC
Following the reproduce steps, I set a default value to a radio button (see screenshot) and saved, then edited again. The defeault value for the radio button is still not rendered (see second screenshot). The black dot should be on value "Two". The default value is saved, I can see it when editing the radio button in tab Options, it just isn't rendered on the dialog edit page. Created attachment 1395248 [details]
Set the default value for radio button
Created attachment 1395250 [details]
Radio button still has no default value rendered
Erik, this looks like the same issue I've been fixing in https://github.com/ManageIQ/ui-components/pull/251 Thanks Roman, yeah I just pulled the latest and it appears to have fixed it. Antonin, please try with the latest build, it should be working now. *** This bug has been marked as a duplicate of bug 1531571 *** |