Bug 748582

Summary: Inconsistent 'new $foo' buttons
Product: [Retired] CloudForms Cloud Engine Reporter: Scott Seago <sseago>
Component: aeolus-conductorAssignee: Angus Thomas <athomas>
Status: CLOSED EOL QA Contact: Rehana <aeolus-qa-list>
Severity: low Docs Contact:
Priority: unspecified    
Version: 1.0.0CC: akarol, athomas, dajohnso, deltacloud-maint, hbrock, ssachdev
Target Milestone: rcKeywords: Reopened
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2020-03-27 19:41:55 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description Scott Seago 2011-10-24 22:02:27 UTC
Description of problem:

Although we've put effort into a consistent presentation of list/filter results, action buttons, etc., the same can not be said for the new/create actions.

For most types, there's an obvious link/button on the top right of the content section with clear text "New $foo" (where foo is Pool, Environment, Provider Account, etc). (minor issue: "New Catalog Entry" says just "Catalog Entry")

The two cases that I find harder to navigate/understand are these:

New User: "+<silhouette>" (this one was the most confusing as I didn't even realize that this was the 'new user' link -- I'd thought that the link had gone missing)

New Provider: This one says 'create new provider' but it's embedded within the list of providers in the 'choose a provider' list.

For "New User" we should either switch to the text buttons we're using everywhere else, or we should add the text in addition to the graphical button. As it is now, I had to use the url text in the bottom of my browser to figure out what the button was supposed to do.

For New Provider, we should probably leave the 'switch providers' menu as-is, but take off the 'New' element and use a new button to the side, consistent with the rest.

Comment 1 wes hayutin 2012-01-03 17:43:08 UTC
adding ce-sprint-next bugs to ce-sprint

Comment 2 Ken Keiter 2012-02-03 12:59:34 UTC
Scott, can you please attach a screenshot of what you're talking about?

Comment 3 RHEL Program Management 2012-03-02 16:44:58 UTC
Development Management has reviewed and declined this request.  You may appeal
this decision by reopening this request.