Bug 1825966

Summary: In the Dev Catalog, when grouped by operators, the operators should be listed alphabetically
Product: OpenShift Container Platform Reporter: Debsmita Santra <dsantra>
Component: Dev ConsoleAssignee: Debsmita Santra <dsantra>
Status: CLOSED ERRATA QA Contact: Gajanan More <gamore>
Severity: low Docs Contact:
Priority: medium    
Version: 4.5CC: aos-bugs, nmukherj
Target Milestone: ---   
Target Release: 4.5.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: No Doc Update
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2020-07-13 17:29:09 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
Alphabetical order in dev catalog none

Description Debsmita Santra 2020-04-20 15:23:50 UTC 
Description of problem:
In the developer catalog, when grouped by operators the operators should be listed alphabetically. The Non-Operators grouping is an exception and should be last. Tiles grouped in the Non-Operators catalog are not operator backed.


Version-Release number of selected component (if applicable):
4.5

How reproducible:
Always

Steps to Reproduce:
1. Go to the Developer catalog
2. Select `Operator` in the `Group-By` dropdown

Actual results:
The operator names are alphabetically sorted

Expected results:
The Operator names should be alphabetically sorted

Additional info:
Comment 3 Debsmita Santra 2020-04-27 06:22:21 UTC 
Actual Result: The operator names are not alphabetically sorted
Comment 4 Gajanan More 2020-04-29 13:13:52 UTC 
Created attachment 1682931 [details]
Alphabetical order in dev catalog
Comment 5 Gajanan More 2020-04-29 13:15:04 UTC 
I have validated the bugzilla on:
Build: 4.5.0-0.nightly-2020-04-29-064431
Browser: Google Chrome Version 81.0.4044.129
Please have a look at the screenshots.
Marking this as verified.
Comment 6 errata-xmlrpc 2020-07-13 17:29:09 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-2020:2409