Project:
View Issue Details[ Jump to Notes ] | [ Issue History ] [ Print ] | |||||||||||
ID | ||||||||||||
0055951 | ||||||||||||
Type | Category | Severity | Reproducibility | Date Submitted | Last Update | |||||||
defect | [POS2] POS | minor | have not tried | 2024-07-09 12:12 | 2024-08-01 14:53 | |||||||
Reporter | plujan | View Status | public | |||||||||
Assigned To | Triage Platform Base | |||||||||||
Priority | normal | Resolution | open | Fixed in Version | ||||||||
Status | scheduled | 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 | SCM revision | |||||||||||
Review Assigned To | ||||||||||||
Regression level | ||||||||||||
Regression date | ||||||||||||
Regression introduced in release | ||||||||||||
Regression introduced by commit | ||||||||||||
Triggers an Emergency Pack | No | |||||||||||
Summary | 0055951: [24Q3] Name showing instead of username in the Login screen | |||||||||||
Description | The feature "User Icons in Login Screen" has in 24Q3 a different behaviour than its functional specification says. According the document, the displayed name should be the "Alias" field and the username if the Alias is not set. The spec for the Phase 1 made difficult to follow statements about using the First Name and Last Name initials for the icon but showing the username. In the screenshots, the full name is shown instead, which does not help to clarify how it should look like. | |||||||||||
Steps To Reproduce | 1. Go to User window 2. Pick a valid user and edit it by changing the First Name by "A" and Last Name by "B" 3. Go to the Login POS page, check that the displayed name is "A B" with an icon "AB" (this is not correct according the functional spec) 4. Edit the user again and add "AB" as alias. 5. Check the displayed login is now "AB" as name as "Ab" as icon (this is correct) 6. Edit the user and remove First Name, Last Name and Alias. Check it is not possible as Name cannot be empty. This means there is no way of showing the username in the POS login page. | |||||||||||
Tags | No tags attached. | |||||||||||
Attached Files | ||||||||||||
![]() |
|||||||||
|
![]() |
|
(0167359) alostale (manager) 2024-07-25 11:43 edited on: 2024-07-25 11:47 |
Definitely the specs are not very clear. In phase 1 [1], rule 1.3 states: When no picture is available in the User window, it should show the first character from the first name and the one from the last name, both in uppercase. Example: Jane Green Smith will display “JG” jane green smith will display “JG” JANE GREEN SMITH will display “JG” If there is only one first name, then the two first characters of this word, the first in uppercase and the second in lowercase.: Example: Jane will display “Ja”. jane will display “Ja”. JANE will display “Ja”. If there is no first name or last name, it should show the two first characters of the user name, the first in uppercase and the second in lowercase. Example: Jane will display “Ja”. jane will display “Ja”. JANE will display “Ja”. It should have a random background color based on the UUID, but the same UUID icon will always have the same background color (i.e. if 432A3439F3GB…is randomly red, it will always be red). The top-right user circle present in portrait mode to access the user popover should be changed also to randomize based on UUID. The color of the text should be black or white following the same logic/algorithm that we have in product keymap buttons In phase 2 [1], rule 1.3 states: In the POS login screen, * If ‘Alias’ is informed, the ‘Alias’ should be displayed instead of the username. * If ‘Alias’ is not informed, the username should be displayed. My understating is the last sentence is incorrect and it should something like: "If 'Alias' is not informed, the rules defined in Phase 1, rule 1.3 should apply". This is how it is currently implemented. Can UX team confirm? --- [1] https://docs.google.com/document/d/1rsBupuhsj8dfW1JvdreH1MwV005iFWFwX0TSM9vffPs/edit [^] [2] https://docs.google.com/document/d/1WYMD9MxSlfwLjXBOoT5xzurhJqEDzBxwQbwf0X1V_24/edit [^] |
(0167454) dbaz (developer) 2024-07-29 15:32 |
One thing is the text displayed in the bubble, if no user picture is provided, that is the first part: When no picture is available in the User window, it should show the first character from the first name and the one from the last name, both in uppercase. Example: Jane Green Smith will display “JG” jane green smith will display “JG” JANE GREEN SMITH will display “JG” If there is only one first name, then the two first characters of this word, the first in uppercase and the second in lowercase.: Example: Jane will display “Ja”. jane will display “Ja”. JANE will display “Ja”. If there is no first name or last name, it should show the two first characters of the user name, the first in uppercase and the second in lowercase. Example: Jane will display “Ja”. jane will display “Ja”. JANE will display “Ja”. It should have a random background color based on the UUID, but the same UUID icon will always have the same background color (i.e. if 432A3439F3GB…is randomly red, it will always be red). The top-right user circle present in portrait mode to access the user popover should be changed also to randomize based on UUID. The color of the text should be black or white following the same logic/algorithm that we have in product keymap buttons And another different thing is the text written below this bubble: In the POS login screen, * If ‘Alias’ is informed, the ‘Alias’ should be displayed instead of the username. * If ‘Alias’ is not informed, the username should be displayed. |
(0167612) AugustoMauch (manager) 2024-08-01 14:53 |
Confirmed by David, if Alias is informed, it will be displayed, if not, the username will be displayed. First and last name will not be displayed |
![]() |
|||
Date Modified | Username | Field | Change |
2024-07-09 12:12 | plujan | New Issue | |
2024-07-09 12:12 | plujan | Assigned To | => Retail |
2024-07-09 12:12 | plujan | Triggers an Emergency Pack | => No |
2024-07-25 10:32 | alostale | Assigned To | Retail => Triage Platform Base |
2024-07-25 11:43 | alostale | Note Added: 0167359 | |
2024-07-25 11:44 | alostale | Note Edited: 0167359 | View Revisions |
2024-07-25 11:46 | alostale | Note Edited: 0167359 | View Revisions |
2024-07-25 11:47 | alostale | Note Edited: 0167359 | View Revisions |
2024-07-25 11:47 | alostale | Status | new => feedback |
2024-07-25 12:18 | alostale | Relationship added | related to 0055106 |
2024-07-29 15:32 | dbaz | Note Added: 0167454 | |
2024-08-01 14:53 | AugustoMauch | Note Added: 0167612 | |
2024-08-01 14:53 | AugustoMauch | Status | feedback => scheduled |
Copyright © 2000 - 2009 MantisBT Group |