Description of problem: 1) It isn't obvious you have to press add to get an env or label to apply 2) The UI gives you a visual clue that not clicking add works (and it doesn't) Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. Go to Add to Project and select a template 2. Fill in envs and labels and add some and leave key/values not added Actual results: If you press add before submitting, the key/values are added Values that are left in the fields and not added aren't added But when you submit the form, the values left in the fields go through the add sequence to go along side the values that were added. So it looks like they were added. Expected results: Make clear before I go on to the next section whether I have done enough to actually add something. Or making clicking add for the last one not necessary. Additional Info: It just isn't clear that clicking Add is necessary or not. Does it mean add another one. Or add this one. It looks like add another one.
Commit pushed to master at https://github.com/openshift/origin-web-console https://github.com/openshift/origin-web-console/commit/08466e85e14340f2fbf403787ae492de7d0566c4 Bug 1333118 - Make for CLI tools a standalone help page
PR https://github.com/openshift/origin-web-console/pull/18#issuecomment-221950664 merged to openshift-web-console, working on backport PR to openshift/ose
backport merged to ose/master
Tested against openshift v3.2.1.1-1-g33fa4ea with IE11, Edge25, Safari9, Firefox46, Chrome 49 openshift v3.2.1.1-1-g33fa4ea kubernetes v1.2.0-36-g4a3f9c5 etcd 2.2.5 Now when key/value uncommitted changes exists, "Create" button is disabled and warning message "Please add or clear this name-value pair" will printed Which I think works well
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-2016:1343