Owner: Architect:

_<Architect is responsible for completing this section to define the
details of the story>_

Story (Required)

As an OpenShift user, I'd like to see the LATEST charts, sorted by release (semver) version.

But today the list is in the order they were released, which makes sense if your chart is single-stream, but not if you are releasing for multiple product version streams (1.0.z, 1.1.z, 1.2.z)

Background (Required)

RHDH has charts for 2 concurrent release streams today, with a 3rd stream coming in June, so we'll have 1.0.z updates after 1.2, and 1.1.z after that. Mixing them together is confusing, especially with the Freshmaker CVE updates.

Acceptance Criteria

One of two implementations:

a) default sorting is by logical semver, with latest being the bottom of the list (default selected) and top of the list being the oldest chart; or

b) UI to allow choosing to sort by release date or version

Development:

QE:
Documentation: Yes/No (needs-docs|upstream-docs / no-doc)

Upstream: <Inputs/Requirement details: Concept/Procedure>/ Not
Applicable

Downstream: <Inputs/Requirement details: Concept/Procedure>/ Not
Applicable

Release Notes Type: <New Feature/Enhancement/Known Issue/Bug
fix/Breaking change/Deprecated Functionality/Technology Preview>

INVEST Checklist

Dependencies identified

Blockers noted and expected delivery timelines set

Design is implementable

Acceptance criteria agreed upon

Story estimated

v

Legend

Unknown

Verified

Unsatisfied