[jbosstools-issues] [JBoss JIRA] (JBIDE-13932) Remove connections from OpenShift Explorer tab on IDE (re)start

[Michelle Murray (JIRA)]

    [ https://issues.jboss.org/browse/JBIDE-13932?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12765138#comment-12765138 ] 

Michelle Murray commented on JBIDE-13932:
-----------------------------------------

Actually, on further investigation, I take this all back. I can see that listing previous connections is useful as the user can just double-click on the connection to open the prefilled connection wizard and re-establish the connection.
                
> Remove connections from OpenShift Explorer tab on IDE (re)start
> ---------------------------------------------------------------
>
>                 Key: JBIDE-13932
>                 URL: https://issues.jboss.org/browse/JBIDE-13932
>             Project: Tools (JBoss Tools)
>          Issue Type: Enhancement
>          Components: openshift
>    Affects Versions: 4.0.0.Final
>            Reporter: Michelle Murray
>            Assignee: Andre Dietisheim
>
> On (re)starting the IDE, previously active connections show in the OpenShift Explorer tab. I think this is probably intended behaviour and not a bug. But I do not think this behaviour is useful for users.
> On (re)starting the IDE, the connections listed in the OpenShift Explorer tab are inactive. To get active connections, a user has to click the 'Connect to OpenShift' icon and still pick a previous or new connection. So I cannot see the benefit to the user of listing previously active connections in the OpenShift Explorer tab.
> I think it would be simpler from a user perspective if the OpenShift Explorer tab was always empty when the IDE starts (since no connections are active). Then, as currently happens, when the user clicks the 'Connect to OpenShift' icon they will see the list of previous connections and can choose from these or pick a new one.

--
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