Red Hat Bugzilla – Bug 1474517
SUI: Drop Down List Dialog does not keep default value for Integer type
Last modified: 2018-02-21 01:56:22 EST
Created attachment 1303859 [details]
No default value
Description of problem:This bug is same as
https://bugzilla.redhat.com/show_bug.cgi?id=1468370 but for SUI .
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. OPS UI shows the default value saved in the dialog.
2. Order the catalog item in SUI , the default value is not displayed.
3. "Choose" option is also not selected .
Created attachment 1303860 [details]
Default value selected in OPS UI
Created attachment 1303861 [details]
Created attachment 1303862 [details]
Appliance : https://10.16.5.146/ui/service
This issue is actually addressed in the dialog system rewrite. https://bugzilla.redhat.com/show_bug.cgi?id=1466340. I will update this ticket once that one is completed and integrated into SUI.
A Pivotal Tracker story has been created for this Bug: https://www.pivotaltracker.com/story/show/149888944
Allen deleted the linked story in Pivotal Tracker
(waiting for review)
Default values is displayed in dropdown but on clicking on the dropdown, the default value is gone and field desc is shown instead . See attached screenshot.
I can open a separate BZ for this if required.
Created attachment 1346282 [details]
So, it looks like the target release is 5.9 and I believe that we have already fixed this in 5.9. Would you be able to test on a 5.9 box?
(In reply to Chris Kacerguis from comment #11)
> So, it looks like the target release is 5.9 and I believe that we have
> already fixed this in 5.9. Would you be able to test on a 5.9 box?
This observation is on 5.9.
I took a deeper look at this issue and here is what I did.
I went into the sample dialog and changed the value type to "Integer"
I then set a default value to "2"
The behavior I noticed in the API is that the API returned a string "[\"2\",\"2\"]". The API should be returning a simple integer of 2 not a string representation of an array. I believe this might not be and issue with the API but more of an issue with the Dialog editor sending back an array when it should be sending a integer as the default_value. I am going to have someone from the Classic UI team take a look and see if it is an issue with editing of dialogs