[ https://issues.jboss.org/browse/JBIDE-17984?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-17984: ------------------------------------- Description: In JBIDE-10541 we added a "Publish Changes" dialog that shows the dirty changes for the local project, allows users to provide a commit msg and to commit/publish changes to OpenShift. In JBIDE-17190 we switched from automatic commit to explicit commit via this dialog when import new/existing OpenShift application. The "Publish Changes" dialog popping up after the OpenShift application was imported (application wizard) proved to be unexpected, disturbing in UX tests. We could get back to automatic commit but this is very much opaque for the user (discussed it in length with [~maxandersen]). We therefore decided to fully drop any commit and push when doing the initial import. We just process our changes and keep the imported project dirty. The user can then push the changes back to OpenShift via the server adapter. was: In JBIDE-10541 we added a "Publish Changes" dialog that shows the dirty changes for the local project, allows users to provide a commit msg and to commit/publish changes to OpenShift. This resulted in having a "Publish Changes" dialog popping up after the OpenShift application was imported (application wizard). UX tests revealed that this dialog is disturbing to users, it is pretty much unexpected for them. We could solve this via automatic commit as we did so far but this is very much opaque for the user (discussed it in length with [~maxandersen]). We therefore decided to fully drop any commit and push when doing the initial import. We just process our changes and keep the imported project dirty. The user can then push the changes back to OpenShift via the server adapter. -- This message was sent by Atlassian JIRA (v6.2.6#6264)