Project:
| View Issue Details[ Jump to Notes ] | [ Issue History ] [ Print ] | |||||||||||
| ID | ||||||||||||
| 0038999 | ||||||||||||
| Type | Category | Severity | Reproducibility | Date Submitted | Last Update | |||||||
| defect | [Retail Modules] Web POS | minor | have not tried | 2018-07-19 14:28 | 2018-07-19 15:21 | |||||||
| Reporter | plujan | View Status | public | |||||||||
| Assigned To | Retail | |||||||||||
| 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 | ||||||||||||
| 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. | |||||||||||
| Tags | No tags attached. | |||||||||||
| Attached Files |  AddingObsoleteProductErrorMessage.png [^] (62,040 bytes) 2018-07-19 14:28
| |||||||||||
 Relationships [ Relation Graph ]
[ Dependency Graph ]
|
|
 Relationships |
|
Notes |
|
|
(0105805) dbaz (developer) 2018-07-19 14:35 |
One note: the error popup when the user tries to add the product to the ticket should remain. There are some products that once they are clicked, they are supposed to be added to the ticket (in this case the error popup should be shown), but there are other ones where the product (stock) card is shown. In those last ones the error is not shown but the product (stock) card. For these last ones, the product (stock) card should not display the 'Add to Receipt' button. |
|
Notes |
|
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 |
|
Issue History |
| Copyright © 2000 - 2009 MantisBT Group |
 |