Uploaded image for project: 'OpenShift Container Platform (OCP) Strategy'
  1. OpenShift Container Platform (OCP) Strategy
  2. OCPSTRAT-518

Console: Customer Happiness (RFEs) for 4.15

    XMLWordPrintable

Details

    • True
    • 100
    • 100% 100%
    • 0
    • 0
    • Program Call

    Description

      Feature Overview

      Console enhancements based on customer RFEs that improve customer user experience.

       

      Goals

      • This Section:* Provide high-level goal statement, providing user context and expected user outcome(s) for this feature
      • …

       

      Requirements

      • This Section:* A list of specific needs or objectives that a Feature must deliver to satisfy the Feature.. Some requirements will be flagged as MVP. If an MVP gets shifted, the feature shifts. If a non MVP requirement slips, it does not shift the feature.

       

      Requirement Notes isMvp?
      CI - MUST be running successfully with test automation This is a requirement for ALL features. YES
      Release Technical Enablement Provide necessary release enablement details and documents. YES

       

      (Optional) Use Cases

      This Section: 

      • Main success scenarios - high-level user stories
      • Alternate flow/scenarios - high-level user stories
      • ...

       

      Questions to answer…

      • ...

       

      Out of Scope

      • …

       

      Background, and strategic fit

      This Section: What does the person writing code, testing, documenting need to know? What context can be provided to frame this feature.

       

      Assumptions

      • ...

       

      Customer Considerations

      • ...

       

      Documentation Considerations

      Questions to be addressed:

      • What educational or reference material (docs) is required to support this product feature? For users/admins? Other functions (security officers, etc)?
      • Does this feature have doc impact?  
      • New Content, Updates to existing content,  Release Note, or No Doc Impact
      • If unsure and no Technical Writer is available, please contact Content Strategy.
      • What concepts do customers need to understand to be successful in [action]?
      • How do we expect customers will use the feature? For what purpose(s)?
      • What reference material might a customer want/need to complete [action]?
      • Is there source material that can be used as reference for the Technical Writer in writing the content? If yes, please link if available.
      • What is the doc impact (New Content, Updates to existing content, or Release Note)?

      Attachments

        Issue Links

          clones

          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
          is cloned by

          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-924 Console: Customer Happiness (RFEs) for 4.16

          • 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
          is related to

          Epic - Created by Jira Software - do not edit or delete. Issue type for a big user story that needs to be broken down. ODC-7108 [4.13] ODC Usability & Customer Happiness Epic

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

          Activity

            People

              amobrem Ali Mobrem
              amobrem Ali Mobrem
              Yufen Chang Yufen Chang
              Olivia Payne Olivia Payne
              Rick Wagner Rick Wagner
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: