Bug 760124 - Create and Update GPG keys should have similar UI - show options in same order.
Summary: Create and Update GPG keys should have similar UI - show options in same order.
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: WebUI
Version: 6.0.1
Hardware: Unspecified
OS: Unspecified
low
low vote
Target Milestone: Unspecified
Assignee: Eric Helms
QA Contact: Katello QA List
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-12-05 13:46 UTC by Corey Welton
Modified: 2019-09-26 13:25 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-08-22 20:55:09 UTC
Target Upstream Version:

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Description Corey Welton 2011-12-05 13:46:42 UTC 
Description of problem:

minor UI nit -

When creating a new GPG key, user is given the option to (a) paste in a new key or (b) upload new key

When updating a GPG key, user is given the option to (a) upload a new key or (b) paste in a new key.

We should choose which option should show up first/second, and have them show up in the same order on both pages.
Comment 1 Mike McCune 2012-01-26 19:39:09 UTC 
mass move to CFSE product.
Comment 2 Eric Helms 2012-02-21 20:19:21 UTC 
1989c9896549e8aabf2cd6196637da100cd7f52a

The create and edit workflows are now in the same order with the name followed by the upload option followed by the key paste option.
Comment 3 Eric Helms 2012-02-21 20:21:39 UTC 
(In reply to comment #2)
> 1989c9896549e8aabf2cd6196637da100cd7f52a
> 
> The create and edit workflows are now in the same order with the name followed
> by the upload option followed by the key paste option.

Wrong commit hash previously. Correct:


ff8c6f25b74c0430109102f36d15d919fba38b7b
Comment 4 Corey Welton 2012-02-23 15:25:44 UTC 
QA Verified.
Comment 5 Mike McCune 2013-08-16 18:11:07 UTC 
getting rid of 6.0.0 version since that doesn't exist
Note You need to log in before you can comment on or make changes to this bug.