Openbravo Issue Tracking System - Retail Modules | |||||
View Issue Details | |||||
ID | Project | Category | View Status | Date Submitted | Last Update |
0038999 | Retail Modules | Web POS | public | 2018-07-19 14:28 | 2018-07-19 15:21 |
Reporter | plujan | ||||
Assigned To | Retail | ||||
Priority | normal | Severity | minor | Reproducibility | have not tried |
Status | new | Resolution | open | ||
Platform | OS | 5 | OS Version | ||
Product Version | main | ||||
Target Version | Fixed in Version | ||||
Merge Request Status | |||||
Review Assigned To | |||||
OBNetwork customer | |||||
Support ticket | |||||
Regression level | |||||
Regression date | |||||
Regression introduced in release | |||||
Regression introduced by commit | |||||
Triggers an Emergency Pack | No | ||||
Summary | 0038999: [RR18Q3] [UX] Usability on webPOS browsing/adding obsolete products should be improved | ||||
Description | Since the introduction of Life Cycle Status, products listed in the webPOS "Browse" section could be marked as "Obsolete". Current flow for this type of products is no different than for regular ones, with the exception that if the user tries to add an obsolete product to a ticket an error message will shown. From an end user perspective, that the error-flow were the normal-flow (ie. the expected behaviour of browsing the list and realising on picking a product that it is an obsolete one) is an usability defect. A user should be able to clearly distinguish which products are voided from the ticket while browsing/searching, not on the "adding" action. | ||||
Steps To Reproduce | 1. Having a product marked as Obsolete in the backend, log in in the webPOS 2. Browse/search the product list. Note that there is no information about the Life Cycle Status of the products. 3. Choose a product that has not been changed (ie. it is still available) 4. As expected, the product can be added to the ticket 5. Choose the product marked as obsolete in step one 6. An error message is shown as in the attached screenshot. | ||||
Proposed Solution | |||||
Additional Information | |||||
Tags | No tags attached. | ||||
Relationships | |||||
Attached Files | AddingObsoleteProductErrorMessage.png (62,040) 2018-07-19 14:28 https://issues.openbravo.com/file_download.php?file_id=11982&type=bug | ||||
Issue History | |||||
Date Modified | Username | Field | Change | ||
2018-07-19 14:28 | plujan | New Issue | |||
2018-07-19 14:28 | plujan | Assigned To | => Retail | ||
2018-07-19 14:28 | plujan | File Added: AddingObsoleteProductErrorMessage.png | |||
2018-07-19 14:28 | plujan | Regression introduced in release | => main | ||
2018-07-19 14:28 | plujan | Triggers an Emergency Pack | => No | ||
2018-07-19 14:35 | dbaz | Note Added: 0105805 | |||
2018-07-19 15:21 | plujan | Regression introduced in release | main => | ||
2018-07-19 15:21 | plujan | version | => main |
Notes | |||||
|
|||||
|
|