Openbravo Issue Tracking System - Retail Modules | |||||
| View Issue Details | |||||
| ID | Project | Category | View Status | Date Submitted | Last Update |
| 0048125 | Retail Modules | Web POS | public | 2021-11-22 15:56 | 2021-12-02 18:59 |
| Reporter | jetxarri | ||||
| Assigned To | marvintm | ||||
| Priority | high | Severity | minor | Reproducibility | always |
| Status | closed | Resolution | fixed | ||
| Platform | OS | 5 | OS Version | ||
| Product Version | |||||
| Target Version | Fixed in Version | RR22Q1 | |||
| Merge Request Status | |||||
| Review Assigned To | marvintm | ||||
| OBNetwork customer | |||||
| Support ticket | |||||
| Regression level | |||||
| Regression date | |||||
| Regression introduced in release | |||||
| Regression introduced by commit | |||||
| Triggers an Emergency Pack | No | ||||
| Summary | 0048125: Create the logic define when a discount can apply or not a promotion regarding the promotion already applied logic | ||||
| Description | Currently, we can manage the application of discount with : - The priorities : this promotion is applied before another promotion - The checkbox “apply next discount” : this promotion will be the last promotion applied on the line or not What it is not possible to manage is compatibility logic between discounts: -p0 is applied -p1 could be applied but is not compatible with p0 (so it is not applied) -p2 is applied and it is compatible with all discounts | ||||
| Steps To Reproduce | -Define 2 generic discounts that they are always applied <-- P0 -Define priority <-- P1 We are not able to say to Web POS not to apply P1 if P0 is applied | ||||
| Proposed Solution | |||||
| Additional Information | |||||
| Tags | No tags attached. | ||||
| Relationships | |||||
| Attached Files | |||||
| Issue History | |||||
| Date Modified | Username | Field | Change | ||
| 2021-11-22 15:56 | jetxarri | New Issue | |||
| 2021-11-22 15:56 | jetxarri | Assigned To | => Retail | ||
| 2021-11-22 15:56 | jetxarri | Triggers an Emergency Pack | => No | ||
| 2021-11-22 20:04 | hgbot | Note Added: 0133264 | |||
| 2021-11-22 20:04 | hgbot | Note Added: 0133265 | |||
| 2021-11-22 20:04 | hgbot | Note Added: 0133266 | |||
| 2021-11-22 20:04 | hgbot | Note Added: 0133267 | |||
| 2021-12-02 07:06 | hgbot | Note Added: 0133447 | |||
| 2021-12-02 07:08 | hgbot | Note Added: 0133448 | |||
| 2021-12-02 07:09 | hgbot | Note Added: 0133449 | |||
| 2021-12-02 07:11 | hgbot | Note Added: 0133450 | |||
| 2021-12-02 07:12 | marvintm | Status | new => scheduled | ||
| 2021-12-02 07:12 | marvintm | Assigned To | Retail => marvintm | ||
| 2021-12-02 07:12 | marvintm | Type | defect => feature request | ||
| 2021-12-02 07:14 | marvintm | Note Added: 0133451 | |||
| 2021-12-02 07:14 | marvintm | Status | scheduled => resolved | ||
| 2021-12-02 07:14 | marvintm | Fixed in Version | => RR22Q1 | ||
| 2021-12-02 07:14 | marvintm | Resolution | open => fixed | ||
| 2021-12-02 07:15 | marvintm | Review Assigned To | => marvintm | ||
| 2021-12-02 07:15 | marvintm | Status | resolved => closed | ||
| 2021-12-02 07:53 | hgbot | Note Added: 0133454 | |||
| 2021-12-02 18:59 | marvintm | Note Added: 0133495 | |||