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

Updates to the OpenShift Express Console

    XMLWordPrintable

Details

    • Enhancement
    • Resolution: Done
    • Major
    • 3.3.0.Beta3
    • None
    • openshift
    • None

    Description

      1) Add to JBoss Perspective
      2) OpenShift Express Console - is not really a "Console"
      3) Add URL for each application - the URL is one of the most important data elements I need to know and it is currently "hidden" in Properties
      4) Add the last updated date time - I would like to know when this application was last "pushed", lasted updated

      And we need to think through the relationship of the OpenShift Express tab and the Servers tab where I need the "server adapter" in order to publish changes. This is a bit confusing, we need to think about adding Publish to the OpenShift tab.

      Attachments

        Issue Links

          is duplicated by

          Feature Request - Feature requests from customers and/or users JBIDE-11195 Consider renaming "OpenShift Express Console" to "OpenShift Explorer" or "OpenShift Navigator"

          • 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

          Feature Request - Feature requests from customers and/or users JBIDE-11193 openshift express console - should be in jboss perspective by default

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

          Feature Request - Feature requests from customers and/or users JBIDE-11629 Make "Details..." available from OpenShift Explorer

          • 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

          Activity

            People

              xcoulon@redhat.com Xavier Coulon
              bsutter@redhat.com Burr Sutter
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: