Bug 837084 - Usability issue on success page when adding cart which has secured web UI link with credentials
Summary: Usability issue on success page when adding cart which has secured web UI lin...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: OKD
Classification: Red Hat
Component: Website
Version: 2.x
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: ---
: ---
Assignee: Steve Goodwin
QA Contact: libra bugs
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-07-02 17:42 UTC by Dan Mace
Modified: 2015-05-15 01:12 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-07-13 23:43:19 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
new visuals for reference (156.57 KB, image/png)
2012-07-10 14:27 UTC, Steve Goodwin
no flags Details

Description Dan Mace 2012-07-02 17:42:19 UTC
Description of problem:

When adding a cartridge which provides a secured web UI (e.g. Jenkins), the resulting success page does not provide any visual contrast or other obvious cues as to the importance of noting the credentials, especially given the lack of a password reset mechanism. If the user does not make note on that single page, the cartridge UI will be rendered forever inaccessible to the user. The lack of visual contrast and cues could cause users to gloss over the page and navigate away.

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


How reproducible:

Add a Jenkins server cartridge, and look at the resulting success page.

Steps to Reproduce:
1.
2.
3.
  
Actual results:

A low-contrast success page which does not provide sufficient warning to the user of the implications of losing the listed credentials.

Expected results:

A more obvious explanation of the ramifications of losing the credentials, as well as more visual contrast to prevent the user from glossing over the success page.

Additional info:

Comment 1 Clayton Coleman 2012-07-03 02:56:31 UTC
Multiple problems here - there should be a way of retrieving this info at anytime, and a better visual display of the attributes when they are retrieved.

Comment 2 Steve Goodwin 2012-07-09 21:28:02 UTC
It would be beneficial if each individual app had it's own "settings" page that would contain this and other key information, so it's accessible to the user at all times.

Looking through the backlog, I couldn't find a user story pertaining to this issue.

Comment 3 Clayton Coleman 2012-07-10 01:53:37 UTC
Steve was going to address the visuals.  Settings is further out - we will have to prioritize it eventually but it's not yet on the radar.

Comment 4 Steve Goodwin 2012-07-10 14:26:02 UTC
<pre> code block styles modified for high contrast with surrounding text.

Comment 5 Steve Goodwin 2012-07-10 14:27:18 UTC
Created attachment 597354 [details]
new visuals for reference

Comment 6 Yujie Zhang 2012-07-11 07:51:07 UTC
(In reply to comment #5)
Tested this issue on devenv_1884, the new visuals for reference has been added.


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