Openbravo Issue Tracking System - POS2 | |||||
View Issue Details | |||||
ID | Project | Category | View Status | Date Submitted | Last Update |
0050634 | POS2 | Core | public | 2022-10-25 16:27 | 2022-11-30 07:36 |
Reporter | hbrasme | ||||
Assigned To | ranjith_qualiantech_com | ||||
Priority | high | Severity | major | Reproducibility | always |
Status | closed | Resolution | fixed | ||
Platform | OS | 5 | OS Version | ||
Product Version | 22Q3 | ||||
Target Version | Fixed in Version | ||||
Merge Request Status | approved | ||||
Review Assigned To | |||||
OBNetwork customer | Gold | ||||
Support ticket | |||||
Regression level | |||||
Regression date | |||||
Regression introduced in release | |||||
Regression introduced by commit | |||||
Triggers an Emergency Pack | No | ||||
Summary | 0050634: [PROMO] The price adjustment discount has different behavior if a % or an amount is defined | ||||
Description | The price adjustment discount type has a different behavior depend on if the defined discount is a % or an amount. See image 'User Cases Comparation'. User Case 1 (% + isMul=No) and User Case 3 (Amt + isMul=No) → same behaviour where there are several lines in the ticket, the discount is splitted by line. User Case 2 (% + isMul=Yes) and User Case 4 (Amt + isMul=Yes) → different behaviour where there are several lines in the ticket - For User Case 2 → The double of the defined discount is applied per each line. KO - For User Case 4 → The discount is splitted by line. OK | ||||
Steps To Reproduce | Create two PriceAdjustment Promotions: *User Case 2 (% + isMul=Yes) *User Case 4 (Amt + isMul=Yes) On the POS2 *Create a ticket for which the User Case 2 applies in several lines --> The double of the defined discount is applied per each line. *Create a ticket for which the User Case 4 applies in several lines --> the discount is spplited by line. Steps to reproduce in livebuilds Backoffice 1) Create discount with type "Price Adjustment", Discount % as "10", Is Multiple as "checked", Units per package as "2" POS 1) Add 4 Products. 2) Discount is correct applied - OK 3) Split receipt line into 4 lines 4) Discount is not correct applied - KO Same problem will occur for ungrouped products | ||||
Proposed Solution | The price adjustment discount type must work in the same way regardless a % discount or an amount discount will be defined in both cases: *Is Multiple=Yes *Is Multiple=No | ||||
Additional Information | |||||
Tags | FASH | ||||
Relationships | |||||
Attached Files | ![]() https://issues.openbravo.com/file_download.php?file_id=17731&type=bug | ||||
Issue History | |||||
Date Modified | Username | Field | Change | ||
2022-10-25 16:27 | hbrasme | New Issue | |||
2022-10-25 16:27 | hbrasme | Assigned To | => Triage Platform Base | ||
2022-10-25 16:27 | hbrasme | File Added: 2141 - Result Grouped Product.png | |||
2022-10-25 16:27 | hbrasme | Triggers an Emergency Pack | => No | ||
2022-10-25 16:27 | hbrasme | File Added: 2141 - Result Split Product.png | |||
2022-10-25 16:34 | rafaroda | Tag Attached: FASH | |||
2022-10-25 16:39 | rafaroda | OBNetwork customer | => Gold | ||
2022-10-25 17:29 | avicente | Priority | normal => high | ||
2022-10-25 17:36 | avicente | Issue Monitored: avicente | |||
2022-10-26 08:43 | hbrasme | Note Added: 0142586 | |||
2022-10-27 15:42 | avicente | Summary | [PROMO] - Advantages - No split of the discount amount if several quantities of the same item => [PROMO] The price adjustment discount has different behavior if a % or an amount is defined | ||
2022-10-27 15:42 | avicente | Description Updated | bug_revision_view_page.php?rev_id=25003#r25003 | ||
2022-10-27 15:42 | avicente | Steps to Reproduce Updated | bug_revision_view_page.php?rev_id=25005#r25005 | ||
2022-10-27 15:42 | avicente | Proposed Solution updated | |||
2022-10-27 16:20 | avicente | Description Updated | bug_revision_view_page.php?rev_id=25006#r25006 | ||
2022-10-27 16:20 | avicente | Steps to Reproduce Updated | bug_revision_view_page.php?rev_id=25007#r25007 | ||
2022-10-27 16:20 | avicente | File Added: User Cases Comparation.png | |||
2022-10-27 16:35 | marvintm | Assigned To | Triage Platform Base => Triage Omni OMS | ||
2022-10-31 10:24 | avicente | Note Deleted: 0142586 | |||
2022-10-31 10:24 | avicente | File Deleted: 2141 - Result Split Product.png | |||
2022-10-31 10:24 | avicente | File Deleted: 2141 - Result Grouped Product.png | |||
2022-11-02 09:46 | marvintm | Assigned To | Triage Omni OMS => Retail | ||
2022-11-02 11:03 | ranjith_qualiantech_com | Assigned To | Retail => ranjith_qualiantech_com | ||
2022-11-02 11:03 | ranjith_qualiantech_com | Status | new => scheduled | ||
2022-11-09 13:50 | ranjith_qualiantech_com | Steps to Reproduce Updated | bug_revision_view_page.php?rev_id=25082#r25082 | ||
2022-11-09 13:52 | hgbot | Merge Request Status | => open | ||
2022-11-09 13:52 | hgbot | Note Added: 0143304 | |||
2022-11-30 07:36 | hgbot | Merge Request Status | open => approved | ||
2022-11-30 07:36 | hgbot | Resolution | open => fixed | ||
2022-11-30 07:36 | hgbot | Status | scheduled => closed | ||
2022-11-30 07:36 | hgbot | Note Added: 0144236 | |||
2022-11-30 07:36 | hgbot | Fixed in Version | => RR23Q1 | ||
2022-11-30 07:36 | hgbot | Note Added: 0144237 |
Notes | |||||
|
|||||
|
|
||||
|
|||||
|
|
||||
|
|||||
|
|