Description of problem: when a dropdown list element is set to use a default value, when the dialog is loaded through classic ui that selection is not shown in the interface but automation wise it is made. this creates confusion at user level. Version-Release number of selected component (if applicable): 5.9.2.4 How reproducible: all the time Steps to Reproduce: 1. create a dialog with a dropdown list (static list of values) 2. set a default selection 3. assign the dialog to a service 4. load the dialog through classic ui, provisioning the service Actual results: the dialog will show "nothing selected" instead of the default selection ; if using an automation based on that value the automation will still think the default has been selected. if trying to select the default value this will lead to confusing results for the rest of the dialog. Expected results: the default value is displayed as selected just like it currently does in self service ui Additional info: self service ui does not have this issue and for the same dialog will display the proper values as being selected.
Hi Felix, I didn't realize you opened a new ticket for the Classic UI dialog issue: Copying my comments from https://bugzilla.redhat.com/show_bug.cgi?id=1576873 ........ Using the customer provided Service Dialog and Automate domains, the Classic UI Service Dialog worked properly for us in a 5.9.2.4 appliance. Dennis raised a very good point in that the customer upgraded, as opposed to installing a new 5.9.2.4 version. Can you find out the customer version prior to the upgrade, and the specific upgrade steps performed? Once we have that information, I'd like to get QE involved to see if we can reproduce the issue. If we're not able to make significant progress today, Erik Clarizio would be available at 11AM tomorrow for a call with the customer for a interactive debugging session. Let me know if you have any questions. Thanks, Tina
I was able to replicate the behaviour on my own appliance on python.usersys.redhat.com which is also updated from 5.9.0 all the way... I'm happy to share access with the system if you need it. the customer will not be available until Tuesday at 11am is 5pm for him.
I ran some tests you need to create two tag categories, "tier_prod" and "tier_no_production" then populate them with a couple tags each so that the automation "tier" used in the sample will not fail. a scripting error causes the dialog to properly display the default selection but if no scripting error occurs you will see the behaviour
Hi Felix, That's great, thanks. I passed along the information to Erik who will be looking into the issue today. Thanks, Tina
Erik and I have determined that this is a patternfly issue because the backend has the right data for the defaults and forcing a jquery reload causes the right values to appear.
We believe this issue is resolved by: https://github.com/ManageIQ/ui-components/pull/295 https://github.com/ManageIQ/manageiq-ui-classic/pull/3945
Able to see default selection of drop down list Verified in Version 5.10.0.23.20181106165157_92dd189