Project:
View Issue Details[ Jump to Notes ] | [ Issue History ] [ Print ] | |||||||||||
ID | ||||||||||||
0033456 | ||||||||||||
Type | Category | Severity | Reproducibility | Date Submitted | Last Update | |||||||
design defect | [Openbravo ERP] B. User interface | minor | always | 2016-07-08 11:03 | 2016-07-11 12:05 | |||||||
Reporter | plujan | View Status | public | |||||||||
Assigned To | psarobe | |||||||||||
Priority | normal | Resolution | open | Fixed in Version | ||||||||
Status | new | Fix in branch | Fixed in SCM revision | |||||||||
Projection | none | ETA | none | Target Version | ||||||||
OS | Any | Database | Any | Java version | ||||||||
OS Version | Database version | Ant version | ||||||||||
Product Version | main | SCM revision | ||||||||||
Review Assigned To | ||||||||||||
Web browser | ||||||||||||
Modules | Core | |||||||||||
Regression level | ||||||||||||
Regression date | ||||||||||||
Regression introduced in release | ||||||||||||
Regression introduced by commit | ||||||||||||
Triggers an Emergency Pack | No | |||||||||||
Summary | 0033456: Usability problems when trying to log in with an expired password | |||||||||||
Description | When the user's password is expired, the login screen fires the flow for asking a new one. Some usability issues observed: - User field gets replaced by "new password" field. From an UX point of view this behaviour is not good practise and should be avoided in favor of keeping the user name field and adding the new fields below. Furthermore since after entering the new password the user is logged in the system. (which is probably another issue) - "New Password" field is marked as non mandatory while "Confirm Password" is mandatory - If both passwords fields are left blank, the error message shown on login is not correct "Invalid user name and password / Enter your username and password" | |||||||||||
Steps To Reproduce | Set an user's password as expired by following this test case https://testlink.openbravo.com/testlink/linkto.php?tprojectPrefix=Communit&item=testcase&id=Communit-10008 [^] and check the issues reported in the description (also see attached screenshot) | |||||||||||
Tags | No tags attached. | |||||||||||
Attached Files | ExpiredPassword.png [^] (42,390 bytes) 2016-07-08 11:03
Password Expiration - Proper.png [^] (55,243 bytes) 2016-07-11 12:05 | |||||||||||
Relationships [ Relation Graph ] [ Dependency Graph ] | |
Notes | |
(0088363) dbaz (developer) 2016-07-11 12:05 |
This project was not developed following the specs. There is no strict need to show the username in the "New Password" screen. The user have just introduced it. In fact, in several systems where this feature is present, the user is not shown in the "Reset Password" screen: http://screencast.com/t/Dx60KzSbM3 [^] There should be a "Continue" and a "Cancel" button, and the "Continue" one should not be enabled until both inputs be filled. * The "Continue" button, logs into the application * The "Cancel" button returns to the "Login" window. The background of both inputs should be white to be coherent with the "Login" screen, where both inputs are mandatory with white background. If both inputs text doesn't match and the "Continue" button is pressed, the red message should remark it. |
Issue History | |||
Date Modified | Username | Field | Change |
2016-07-08 11:03 | plujan | New Issue | |
2016-07-08 11:03 | plujan | Assigned To | => platform |
2016-07-08 11:03 | plujan | File Added: ExpiredPassword.png | |
2016-07-08 11:03 | plujan | Modules | => Core |
2016-07-08 11:03 | plujan | Triggers an Emergency Pack | => No |
2016-07-11 09:49 | alostale | Assigned To | platform => dbaz |
2016-07-11 09:49 | alostale | Type | defect => design defect |
2016-07-11 11:59 | alostale | Assigned To | dbaz => psarobe |
2016-07-11 12:05 | dbaz | Note Added: 0088363 | |
2016-07-11 12:05 | dbaz | File Added: Password Expiration - Proper.png |
Copyright © 2000 - 2009 MantisBT Group |