Bug 1480248

Summary:	"Create SSH key" GUI button incorrectly named
Product:	Red Hat Satellite	Reporter:	Charles Wood <chwood>
Component:	Users & Roles	Assignee:	satellite6-bugs <satellite6-bugs>
Status:	CLOSED ERRATA	QA Contact:	Peter Ondrejka <pondrejk>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	6.3.0	CC:	bkearney, dhlavacd, jcallaha, mhulan, mmccune, rohoover, sgraessl
Target Milestone:	6.4.0	Keywords:	EasyFix, Triaged, UserExperience
Target Release:	Unused
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2018-10-16 19:30:45 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:

Comment 1 Marek Hulan 2017-08-10 14:14:07 UTC

Thanks for the report.

Rox, does this make sense after we converted all buttons from new to create? Would it be intuitive? I suppose the reasoning behind this was that user creates new resource, similar to e.g. Domain. Domain also exist somewhere on DNS server and we're just adding it to Foreman.

Comment 2 Roxanne Hoover 2017-08-11 14:49:18 UTC

Yes this change makes sense.

This is a content strategy issue in that we need to define what we mean by add, new, create and apply those terms consistently.

Comment 4 Sebastian Gräßl 2017-08-28 14:23:34 UTC

Created redmine issue http://projects.theforeman.org/issues/20763 from this bug

Comment 5 Satellite Program 2017-08-31 22:09:32 UTC

Moving this bug to POST for triage into Satellite 6 since the upstream issue http://projects.theforeman.org/issues/20763 has been resolved.

Comment 6 Peter Ondrejka 2018-05-30 14:46:52 UTC

Verified on 6.4 snap 5

Comment 7 Bryan Kearney 2018-10-16 19:30: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/RHSA-2018:2927