Feature Overview (aka. Goal Summary)

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

<your text here>

Goals (aka. expected user outcomes)

The observable functionality that the user now has as a result of receiving
this feature. Include the anticipated primary user type/persona and which
existing features, if any, will be expanded.

<your text here>

Requirements (aka. Acceptance Criteria):

Target for 1.3 Release:

• Automate upgrade path scenarios
  • RHIDP-828,
  • RHIDP-827,
  • RHIDP-2914
• Automate E2E with operator and add it to nightlies 
  • RHIDP-2919

• Automate sign in scenarios[ RHDH Prioritization of Auth Providers|https://docs.google.com/document/d/1OSHIg8dW8qtGe_zJfKFMmZRD-fFyWL7dsxtjsz3OAbA/edit]
  • [Guest, GitHub and Google sign automated already]
  • RHIDP-756
  • RHIDP-2817

• DB version support (Verify TLS config with Postgres in Amazon RDS and Azure DB, multiple versions of Postgres), for using both Operator and HELM chart
  • RHIDP-2915
  • RHIDP-2916
  • RHIDP-2917
  • RHIDP-2918

Out of Scope (Optional)

High-level list of items that are out of scope.

<your text here>

Customer Considerations (Optional)

Provide any additional customer-specific considerations that must be made
when designing and delivering the Feature. Initial completion during
Refinement status.

<your text here>

Documentation Considerations

Provide information that needs to be considered and planned so that
documentation will meet customer needs. If the feature extends existing
functionality, provide a link to its current documentation.

<your text here>