Openbravo Issue Tracking System - POS2 | ||||||||||||
View Issue Details | ||||||||||||
ID | Project | Category | View Status | Date Submitted | Last Update | |||||||
0056085 | POS2 | Fashion | public | 2024-07-22 17:12 | 2024-07-23 07:09 | |||||||
Reporter | philippe_mui | |||||||||||
Assigned To | Retail | |||||||||||
Priority | urgent | Severity | major | Reproducibility | always | |||||||
Status | closed | Resolution | duplicate | |||||||||
Platform | OS | 5 | OS Version | |||||||||
Product Version | ||||||||||||
Target Version | Fixed in Version | |||||||||||
Merge Request Status | ||||||||||||
Review Assigned To | guillermogil | |||||||||||
OBNetwork customer | ||||||||||||
Support ticket | ||||||||||||
Regression level | ||||||||||||
Regression date | ||||||||||||
Regression introduced in release | ||||||||||||
Regression introduced by commit | ||||||||||||
Triggers an Emergency Pack | No | |||||||||||
Summary | 0056085: RM-15551 Print Labels of Overlapping price exceptions appear in double/triple and search by scan is KO | |||||||||||
Description | In POS, when a user wants to print a product that has 2 or more price excpetions overlapping on a same date, the price displayed is wrong and an error message appears when it is scanned. Expected results : the last price exception created should be taken into account and this one only should be displayed on POS when scanning the product with price exception, the user should not have an error message https://openbravo.atlassian.net/browse/RM-15551 [^] | |||||||||||
Steps To Reproduce | Steps to reproduce : Log in BO and go to Product window Choose product P and create a Price exception on it with Unit price = 250€, List Price = 250€ starting on 15/07/2024 and no end date Go to Commercial Operation window and create an opecom with Product P with Unit Price = 175€ from 16/07/2024 to 20/07/2024 Create a 2nd opecom with Product P with Unit Price = 150€ from 18/07/2024 to 20/07/2024 Log in POS and go to Print label screen Select the overlapped date 19/07/2024, select the template and click on next Scan Product P Current result : An error message appear as there are 3 price exceptions conflicting Expected result : Scan is successful as it takes the last created price expection created in step 4. type the name of Product P and search Current result : 3 results appear for Product P and when ticking one of them, all 3 are selected Expected result : Only 1 result appears for Product P and it is the price expection lastly created in step 4. that is taken into account See video : https://drive.google.com/file/d/1ZVhmroRq3N_IweQcksxhnGaQmTqZ9L-_/view?usp=drive_linkConnect [^] your Google account | |||||||||||
Proposed Solution | ||||||||||||
Additional Information | ||||||||||||
Tags | FASH | |||||||||||
Relationships |
| |||||||||||
Attached Files | ||||||||||||
Issue History | ||||||||||||
Date Modified | Username | Field | Change | |||||||||
2024-07-22 17:12 | philippe_mui | New Issue | ||||||||||
2024-07-22 17:12 | philippe_mui | Assigned To | => Retail | |||||||||
2024-07-22 17:12 | philippe_mui | Triggers an Emergency Pack | => No | |||||||||
2024-07-22 17:12 | philippe_mui | Tag Attached: FASH | ||||||||||
2024-07-23 05:27 | guillermogil | Status | new => acknowledged | |||||||||
2024-07-23 07:00 | Rajesh_18 | Relationship added | duplicate of 0056005 | |||||||||
2024-07-23 07:08 | Rajesh_18 | Status | acknowledged => scheduled | |||||||||
2024-07-23 07:09 | Rajesh_18 | Review Assigned To | => guillermogil | |||||||||
2024-07-23 07:09 | Rajesh_18 | Status | scheduled => closed | |||||||||
2024-07-23 07:09 | Rajesh_18 | Resolution | open => duplicate |
There are no notes attached to this issue. |