Bug 1819668 - Keep case consistent on the operand creation page
Summary: Keep case consistent on the operand creation page
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Management Console
Version: 4.5
Hardware: Unspecified
OS: Unspecified
unspecified
low
Target Milestone: ---
: 4.5.0
Assignee: Robb Hamilton
QA Contact: Yadan Pei
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-04-01 09:42 UTC by shahan
Modified: 2020-07-13 17:25 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: No Doc Update
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-07-13 17:24:45 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github openshift console pull 4979 0 None closed Bug 1819668: Make label casing consistent in create operand toggle 2020-06-23 09:44:32 UTC
Red Hat Product Errata RHBA-2020:2409 0 None None None 2020-07-13 17:25:09 UTC

Description shahan 2020-04-01 09:42:09 UTC
Description of problem:
Keep case consistent on the operand creartion page

Version-Release number of selected component (if applicable):
4.5.0-0.nightly-2020-03-31-203533

How reproducible:
Always

Steps to Reproduce:
1. install Prometheus operator from operatorhub
2. try to create "Prometheus Rule" operand 
3. check the creation page 

Actual results:
 The toggle text for "Configure via" looks: Form view & YAML View

Expected results:
Form view & YAML View should keep case consistent, seems the lower case of first letter better.

Additional info:

Comment 3 Yadan Pei 2020-04-10 07:58:10 UTC
Now on Operand creation page, the two toggled view is 'Form View' and  'YAML View'

Verified on     4.5.0-0.nightly-2020-04-09-192237

Comment 5 errata-xmlrpc 2020-07-13 17:24:45 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


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