Uploaded image for project: 'Tools (JBoss Tools)'
  1. Tools (JBoss Tools)
  2. JBIDE-19759

Application wizard: cannot launch v3 application wizard via File->New->OpenShift

    XMLWordPrintable

Details

    • Sprint #3 May 2015, Sprint #4 May 2015, Sprint #5 Jun 2015, Sprint #6 July 2015
    • Hide
      1. EXEC: launch application wizard via File->New->OpenShift->OpenShift application
      2. ASSERT: connection page shows up
      3. EXEC: use an existing/create a new OpenShift v3 connetion and hit "Next"

      Result:

      upcoming page is a v2 page and is all blank (which is expected and no errors)

      Expected result:
      upcoming page should be a v3 page that allows me to create a v3 project

      Show
      EXEC: launch application wizard via File->New->OpenShift->OpenShift application ASSERT: connection page shows up EXEC: use an existing/create a new OpenShift v3 connetion and hit "Next" Result: upcoming page is a v2 page and is all blank (which is expected and no errors) Expected result: upcoming page should be a v3 page that allows me to create a v3 project

    Description

      If you launch the application wizard via File->New->OpenShift you can only create OpenShift v2 applications. I should get v3 pages if I select a v3 connection in the 1st wizard page with the connection credentials. Currently if I select a v2 connection I can create v2 applications. If I select a v3 connection the wizard is non-functional.
      This is very important since that's what a newbie user will come across when hitting "New OpenShift Application" from central.

      Attachments

        Issue Links

          duplicates

          Feature Request - Feature requests from customers and/or users JBIDE-20058 Openshift Application Wizard: No wizard for OpenShift 3 connections present. error is shown if wizard is opened from Central or via File/New

          • Critical - To be worked on immediately following BLOCKER issues.
          • Closed

          Bug - A problem that impairs or prevents the functions of the product. JBIDE-20156 Connection wizard: can't create new v3 application when launching wizard from Central

          • Minor - To be worked after urgent, high, and medium priorities are resolved. This term is chosen when the severity of the issue is low, or the complexity or effort to correct it may be higher, relatively speaking. For low priority issues, known workarounds exist or are not needed due to the trivial effort needed to address the issue.
          • Closed
          incorporates

          Enhancement - An enhancement to or refactoring of existing functionality that is not configurable by an end user (typically a change made by an internal team that affects users) JBIDE-19817 Application wizard: v3 application wizard needs to be able to react to changing connections

          • Blocker - To be worked above all other priorities. This term is chosen when the severity of the issue is very high, has no workaround, or the effort for the change is comparatively low. Issues that may be very publicly visible and could generate significant media attention may also drive a higher priority.
          • Closed
          is caused by

          Enhancement - An enhancement to or refactoring of existing functionality that is not configurable by an end user (typically a change made by an internal team that affects users) JBIDE-20082 Application wizard: it's not userfriendly

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed
          relates to

          Feature Request - Feature requests from customers and/or users JBIDE-20266 v3 Application wizard: should be able to manage projects in application wizard

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed

          Enhancement - An enhancement to or refactoring of existing functionality that is not configurable by an end user (typically a change made by an internal team that affects users) JBIDE-21084 Connection/application wizard: reconnects if you get back and forth to the connection page

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed

          Enhancement - An enhancement to or refactoring of existing functionality that is not configurable by an end user (typically a change made by an internal team that affects users) JBIDE-21085 Connection/application wizard: reconnects if you get back and forth to the connection page

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed

          Activity

            People

              adietish@redhat.com André Dietisheim
              adietish@redhat.com André Dietisheim
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: