Bug 1722880 - missing sorting options for Status and Last Updated in APIs list of Installed Operator
Summary: missing sorting options for Status and Last Updated in APIs list of Installed...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Management Console
Version: 4.1.0
Hardware: Unspecified
OS: Unspecified
unspecified
low
Target Milestone: ---
: 4.2.0
Assignee: Samuel Padgett
QA Contact: Yadan Pei
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-06-21 14:57 UTC by Irina Gulina
Modified: 2019-10-16 06:32 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: No Doc Update
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-10-16 06:32:20 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)
screenshot for comment #0 (203.15 KB, image/png)
2019-06-21 14:57 UTC, Irina Gulina 		no flags Details
View All


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2019:2922 0 None None None 2019-10-16 06:32:32 UTC

Description Irina Gulina 2019-06-21 14:57:03 UTC 
Created attachment 1583267 [details]
screenshot for comment #0

Description of problem:
There is an option to sort Operator Instnaces by Name, Labe and Type, but I'd also like to sort them by Status and Last Update. Right now those are not clickable.

Version-Release number of selected component (if applicable):
quay.io/openshift-release-dev/ocp-v4.0-art-dev@sha256:e6b3e376fd5e0e69d65d12f75e349691e21b155b196618dcbfc3cd9865c343cf

Catalog -> Installed Operators -> Pic one Installed -> All Instances Tab
the screenshot attached
Comment 1 Samuel Padgett 2019-07-03 17:40:22 UTC 
https://github.com/openshift/console/pull/1903
Comment 3 XiaochuanWang 2019-07-08 09:04:16 UTC 
Both Status and Last Update have order icon. 
Verified on registry.svc.ci.openshift.org/ocp/4.2-2019-07-08-052647@sha256:432a7353f9133eff713844c7a6f2e50e793b2b0cdddc76bd09e9106985c20270
Comment 4 errata-xmlrpc 2019-10-16 06:32:20 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2019:2922
Note You need to log in before you can comment on or make changes to this bug.