Bug 1512461

Summary:	Should capitalize the first letter for MySQL on the home page
Product:	OpenShift Container Platform	Reporter:	shahan <hasha>
Component:	Management Console	Assignee:	Jakub Hadvig <jhadvig>
Status:	CLOSED ERRATA	QA Contact:	Yadan Pei <yapei>
Severity:	medium	Docs Contact:
Priority:	high
Version:	3.7.0	CC:	aos-bugs, jforrest, jhadvig, jokerman, mmccomas, spadgett, trankin
Target Milestone:	---
Target Release:	3.7.z
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	No Doc Update
Doc Text:	undefined	Story Points:	---
Clone Of:		Environment:
Last Closed:	2018-04-05 09:30:40 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:

Description shahan 2017-11-13 09:51:49 UTC

Description of problem:
 Should capitalize the first letter for MySQL on the home page

Version-Release number of selected component (if applicable):
v3.7.7 

How reproducible:
Always

Steps to Reproduce:
1. Login in web console, and click Databases-> mySQL
2.
3.

Actual results:
 The the first letter of mySQL in sub-category is lower case.
Expected results:
 Should be "MySQL", cause it's a proper noun.

Additional info:

Comment 3 Samuel Padgett 2017-11-13 14:47:19 UTC

https://github.com/openshift/origin-web-console/pull/2497

Comment 4 Samuel Padgett 2017-11-13 14:55:17 UTC

(In reply to Samuel Padgett from comment #3)
> https://github.com/openshift/origin-web-console/pull/2497

The above PR is for the enterprise-3.7 branch. The fix for master is

https://github.com/openshift/origin-web-console/pull/2498

Comment 6 Samuel Padgett 2017-12-01 18:51:14 UTC

3.7.z fix: https://github.com/openshift/origin-web-console/pull/2551

Comment 9 shahan 2018-03-01 06:34:36 UTC

Checked in OpenShift Master v3.7.35, the bug has been fixed.

Comment 13 errata-xmlrpc 2018-04-05 09:30:40 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-2018:0636