[ https://issues.jboss.org/browse/JBIDE-15597?page=com.atlassian.jira.plugi... ] Andre Dietisheim edited comment on JBIDE-15597 at 10/9/13 11:18 AM: -------------------------------------------------------------------- [~mwigglesworth-redhat] As discussed having the button in the 2nd page is IMHO not a good idea. The 2nd page is all about the local workspace "project" as opposed to the remote "application" in OpenShift. The env vars are only concerning the remote OpenShift "application", thus the widgets should make it to the 1st page (or an additional page that is concerning the OpenShift "application"). The 2nd thing that we discussed, the label/text input that shows you if there are env vars set or not: you were completely convinced that this was only additional clutter and that you would have to hit the button and look at the actual values anyway. I get this but after discussing things with [~maxandersen] we still thought that this label could make sense. Env variables would change the way an application is created. The actual request will differ with or without them. Having a brief information in the UI that shows if the app is created with or without env vars ("yes the app is created WITH env vars" or "no it'll get created without any env vars") is a valuable information that matters for the user. was (Author: adietish): [~mwigglesworth-redhat] As discussed having the button in the 2nd page is IMHO not a good idea. The 2nd page is all about the local workspace "project" as opposed to the remote "application" in OpenShift. The env vars are only concerning the remote OpenShift "application", thus the widgets should make it to the 1st page (or an additional page that is concerning the OpenShift "application"). The 2nd thing that we discussed, the label/text input that shows you if there are env vars set or not: you were completely convinced that this was only additional clutter and that you would have to hit the button and look at the actual values anyway. I get this but after discussing things with [~maxandersen] we still thought that this label could make sense. Env variables would change the way an application is created. The actual request will differ with or without them. Having a brief information in the UI that shows if the app is created with or without env vars ("yes the app is created WITH env vars" or "no it'll get created without any env vars") is a valuable information for the user. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira