Uploaded image for project: 'OpenShift Request For Enhancement'
  1. OpenShift Request For Enhancement
  2. RFE-6279

RFE Template (Description Field)

XMLWordPrintable

    • Icon: Feature Request Feature Request
    • Resolution: Done
    • Icon: Undefined Undefined
    • None
    • None
    • None
    • None
    • False
    • None
    • False
    • Not Selected

      DO NOT DELETE HEADERS. THIS BREAKS AUTOMATION AND WILL CAUSE UNNECESSARY REJECTION OF THE REQUEST

      1. Feature Overview (aka. Goal Summary)

      An elevator pitch (value statement) that describes the Feature in a clear, concise way.

      <your text here>

      2. Technical Goals (aka. expected user outcomes)

      Please describe what the feature will achieve from a technical perspective. What is the current state of the product being used and how would it change? Please try to outline clear, achievable goals.

      <your text here>

      3. Business Goals (aka. expected user business requirements)

      Please describe how the feature will impact the customer from a business perspective. What are the expected business requirements to consider during implementation of the feature enhancement and how would these impact user business.

      <your text here>

      Background (Optional)

      Provide any additional context is needed to frame the feature.

      <your text here>

      Use Cases (Optional):

      _Include use case diagrams, main success scenarios, alternative flow scenarios.

      <your text here>

       

      Anyone reviewing this Feature needs to know which deployment configurations that the Feature will apply to (or not) once it's been completed. Please fill in, to the best of your knowledge, the following table.{color}

      Deployment considerations List applicable specific needs (N/A = not applicable)
      Self-managed, managed, or both  
      Platform (Standalone (Classic), Hosted Control Planes, ARO, ROSA, OSD AWS, OSD GCP, etc)  
      Environment (Virtual, Bare-Metal, AWS, GCP, Azure, Oracle Cloud, Alibaba, etc)  
      Multi node, Compact (three node), or Single node (SNO), or all  
      Cluster Size (# nodes)  
      Connected / Restricted Network  
      Architectures, e.g. x86_x64, ARM (aarch64), IBM Power (ppc64le), and IBM Z (s390x)  
      Operator compatibility  
      Required Openshift Release Version  
      UI need (e.g. OpenShift Console, dynamic plugin, OCM)  
      Permissions added/modified (Note: For a managed service, there is a 4+ weeks lead time)  
      Other (please specify)  

              rh-ee-npng Nick Png
              rh-ee-npng Nick Png
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated:
                Resolved: