Mailing-List: contact cloudstack-users-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: cloudstack-users@incubator.apache.org
Received-SPF: pass (nike.apache.org: domain of Sonny.Chhen@citrix.com
 designates 66.165.176.89 as permitted sender)
From: Sonny Chhen <Sonny.Chhen@citrix.com>
To: "cloudstack-users@incubator.apache.org"
	<cloudstack-users@incubator.apache.org>
Date: Tue, 7 Aug 2012 10:42:20 -0700
Subject: RE: really bad UI design
Thread-Topic: really bad UI design
Thread-Index: Ac10wz+FKFOWYnwRTx6Y9sNxnxMkSQAADRbA
Message-ID: 
 <7914B38A4445B34AA16EB9F1352942F1012F0E1E9040@SJCPMAILBOX01.citrite.net>
References: <be4b7a90bdc723d8afef78e6f464f9e6.squirrel@www.inforelay.com>
In-Reply-To: <be4b7a90bdc723d8afef78e6f464f9e6.squirrel@www.inforelay.com>
Accept-Language: en-US
Content-Language: en-US
acceptlanguage: en-US
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0

Hello,

Thank you for your feedback. We are constantly working to improve the UIX o=
f CloudStack as well as new features that are being implemented. I believe =
the  first issue you mentioned already has a bug attached to it in Jira and=
 we are working to rectify it. Can you please file an "improvement" ticket =
at http://bugs.cloudstack.org for the second issue you mentioned? We apprec=
iate all forms of feedback and look to improving CloudStack to its full pot=
ential.

Thanks You and Best Regards,


Sonny H. Chhen
Manager of User Interface & User Experience | Citrix Systems - CloudPlatfor=
m
4988 Great America Parkway, Santa Clara, CA=A0 95054, USA=A0=A0=A0=A0=A0=A0=
=A0=A0=A0=A0=A0=A0=20

-----Original Message-----
From: mpatton@inforelay.com [mailto:mpatton@inforelay.com]=20
Sent: Tuesday, August 07, 2012 10:35 AM
To: cloudstack-users@incubator.apache.org
Subject: really bad UI design

I realize I'm new to CloudStack and all but these errors are so fundamental=
 they shouldn't exist in the first place let alone after all this time.

1. no password confirmation when changing value - the field is hidden so yo=
u can't see what you typed. Either visually un-hide what the user is typing=
 or at the very LEAST have a 2nd field where they must repeat their entry.

Furthermore, it is standard practice to require the user to provide the old=
 password before accepting a new value.

2. In user management, clearly there is the concept of groups if evidenced =
only in the silliness of "accounts/admin/users/admin" before one can change=
 the 'admin' user account's password. At the very least introduce the word =
"group" at the top level. I suggest renaming the 'admin' group to 'cloud ad=
mins' or 'super-users' or something that denotes their supreme rights.