Bug 2069193 - while checking cluster operator from web console. clicking on the header "Version" or "status", I expect the list to be sorted according to the values in that column. It seems that the sorting is done based on the name of the operator instead.
Summary: while checking cluster operator from web console. clicking on the header "V...
Keywords:
Status: CLOSED DUPLICATE of bug 2066298
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Management Console
Version: 4.9
Hardware: All
OS: Other
medium
medium
Target Milestone: ---
: ---
Assignee: Jakub Hadvig
QA Contact: Yadan Pei
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-03-28 12:58 UTC by bshaw
Modified: 2022-03-29 09:08 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2022-03-28 15:37:19 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
while checking cluster operator from web console. clicking on the header "Version" or "status", I expect the list to be sorted according to the values in that column. It seems that the sorting is do (104.35 KB, image/png)
2022-03-28 12:58 UTC, bshaw
no flags Details

Description bshaw 2022-03-28 12:58:36 UTC
Created attachment 1868708 [details]
while checking cluster operator from web console.  clicking on  the header "Version" or "status", I expect the list to be sorted according to the values in that column. It seems that the sorting is do

Description of problem:

while checking cluster operator from web console.  clicking on  the header "Version" or "status", I expect the list to be sorted according to the values in that column. It seems that the sorting is done based on the name of the operator instead. Please refer attached screen shot
Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 1 Robb Hamilton 2022-03-28 15:37:19 UTC

*** This bug has been marked as a duplicate of bug 2066298 ***


Note You need to log in before you can comment on or make changes to this bug.