[jbosstools-issues] [JBoss JIRA] (JBIDE-20716) Connection wizard: Switch from OpenShift 3 server type to OpenShift 2 triggers usage of default server

Andre Dietisheim (JIRA) issues at jboss.org
Tue Jun 6 05:35:00 EDT 2017


     [ https://issues.jboss.org/browse/JBIDE-20716?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Andre Dietisheim updated JBIDE-20716:
-------------------------------------
    Fix Version/s: 4.5.0.AM2
                       (was: 4.5.0.AM1)


> Connection wizard: Switch from OpenShift 3 server type to OpenShift 2 triggers usage of default server
> ------------------------------------------------------------------------------------------------------
>
>                 Key: JBIDE-20716
>                 URL: https://issues.jboss.org/browse/JBIDE-20716
>             Project: Tools (JBoss Tools)
>          Issue Type: Enhancement
>          Components: openshift
>    Affects Versions: 4.3.0.CR1
>            Reporter: Marián Labuda
>            Priority: Minor
>              Labels: connection_wizard, openshift_v3
>             Fix For: 4.5.0.AM2
>
>   Original Estimate: 1 hour
>  Remaining Estimate: 1 hour
>
> In a New Connection dialog if OpenShift 3 server type is selected and there is no server URL then switch to OpenShift 2 server type checks (enables) the Use default Server checkbox. We should have consistent behavior in switching between OpenShift 2 and OpenShift 3. Because if there is a server URL for OpenShift X server type and I switch to OpenShift Y server type, the URL value persists and checkbox is not being checked.
> We should not check the Use default Server check box upon switching from OpenShift 3 to OpenShift 2 server type with empty URL.



--
This message was sent by Atlassian JIRA
(v7.2.3#72005)



More information about the jbosstools-issues mailing list