Uploaded image for project: 'OpenShift Dev Console'
  1. OpenShift Dev Console
  2. ODC-7108

[4.13] ODC Usability & Customer Happiness Epic

    XMLWordPrintable

Details

    • [4.13] ODC Usability & Customer Happiness Epic
    • False
    • None
    • False
    • Green
    • To Do
    • Impediment
    • 0
    • 77
    • 77% 77%
    • M
    • Not Supported

    Description

      Problem:

      Address outstanding usability issues as well as implement some RFEs

      Acceptance criteria:

      1. Allow users to see which pods are receiving traffic
        1. In Resources tab of side panel when showing pods
        2. In Pods tab of related resources ( Service, Deployment, Deployment Config )
        3. In Pods list view in context of a namespace OR in All Namespaces, the user should be able to select this column through the managed column component
        4. If a Pod is receiving traffic, note that on the Pod detail page
      2. Update Helm terminology to use Create/Delete Helm Release
        1. CTA should Create on Helm Chart side panel
        2. Title of form should be Create Helm Release
        3. CTA of form should be Create
        4. Update the empty state of the Helm Releases page
        5. Update the Uninstall CTA to be Delete
        6. Update the Uninstall Helm Chart flow to be Delete Helm Release

      Dependencies (External/Internal)

      None

      Exploration

      Miro board

      Notes

      Attachments

        Issue Links

          is documented by

          Story - Created by Jira Software - do not edit or delete. Issue type for a user story. RHDEVDOCS-4829 Doc: ODC Usability & Customer Happiness Epic

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

          Feature - Capability or a well-defined set of functionality that delivers business value. Features can include additions or changes to existing functionality. Features can easily span multiple teams, and potentially multiple releases. OCPSTRAT-220 Console: Customer Happiness (RFEs) for 4.14

          • Normal - To be worked after urgent and high priorities are resolved. This term is chosen when the severity of an issue is relatively close to the level of effort to fix it. The existence of an easily implemented workaround can also lead to this priority level instead of a higher priority.
          • New

          Feature - Capability or a well-defined set of functionality that delivers business value. Features can include additions or changes to existing functionality. Features can easily span multiple teams, and potentially multiple releases. OCPPLAN-8030 Console: Customer Happiness (RFEs) for 4.8-4.12

          • Normal - To be worked after urgent and high priorities are resolved. This term is chosen when the severity of an issue is relatively close to the level of effort to fix it. The existence of an easily implemented workaround can also lead to this priority level instead of a higher priority.
          • In Progress

          Feature - Capability or a well-defined set of functionality that delivers business value. Features can include additions or changes to existing functionality. Features can easily span multiple teams, and potentially multiple releases. OCPSTRAT-37 Console: Customer Happiness (RFEs) for 4.13

          • 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 - Capability or a well-defined set of functionality that delivers business value. Features can include additions or changes to existing functionality. Features can easily span multiple teams, and potentially multiple releases. OCPSTRAT-518 Console: Customer Happiness (RFEs) for 4.15

          • 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
          links to

          GitHub openshift/openshift-docs#55909: Changes for RHDEVDOCS-4829 Doc: ODC Usability & Customer Happiness Epic

          1.
          		 Docs Tracker Sub-task Closed Undefined Unassigned
          2.
          		 PX Tracker Sub-task Closed Undefined Unassigned
          3.
          		 QE Tracker Sub-task Closed Undefined Sanket Pathak
          4.
          		 TE Tracker Sub-task Closed Undefined Rick Wagner

          Activity

            People

              dsantra12 Debsmita Santra
              sdoyle@redhat.com Serena Nichols
              Debsmita Santra Debsmita Santra
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: