Project:
| View Issue Details[ Jump to Notes ] | [ Issue History ] [ Print ] | |||||||
| ID | ||||||||
| 0056639 | ||||||||
| Type | Category | Severity | Reproducibility | Date Submitted | Last Update | |||
| defect | [POS2] Core | minor | have not tried | 2024-10-03 12:16 | 2024-11-07 19:00 | |||
| Reporter | malsasua | View Status | public | |||||
| Assigned To | Bimla_vm | |||||||
| Priority | normal | Resolution | open | Fixed in Version | ||||
| Status | closed | 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 | SCM revision | |||||||
| Merge Request Status | ||||||||
| Review Assigned To | guilleaer | |||||||
| OBNetwork customer | Gold | |||||||
| Support ticket | ||||||||
| Regression level | ||||||||
| Regression date | ||||||||
| Regression introduced in release | ||||||||
| Regression introduced by commit | ||||||||
| Triggers an Emergency Pack | No | |||||||
| Summary | 0056639: Combo fixed discount is informed in the line although the combo was not applied | |||||||
| Description | When there are two combo fixed price discounts configured for the same products, and one has got a higher priority than the other, with the flag: "apply next discount: false", in the POS, in the line info, the two combo discounts name are displayed | |||||||
| Steps To Reproduce | BO: . create a new combo fixed price discount: - name: test1 - priority: 1 - apply next discount: No - combo fixed price: 42 - new Family: - name F1 - qty: 2 - max qty: 2 - add product - Crampons 10 point . create a new combo fixed price discount: - name: test2 - priority: (empty) - apply next discount: Yes - combo fixed price: 25 - new Family: - name F1 - qty: 1 - max qty: 1 - add product - Crampons 10 point POS: - add product: Crampons 10 point - qty 2 Total ticket 42 € -> it is OK In the line description, the 2 combo names are displayed (see attachment) -> KO only test1 combo name should be displayed | |||||||
| Tags | No tags attached. | |||||||
| Attached Files |  combo.png [^] (25,030 bytes) 2024-10-03 12:17
| |||||||
 Relationships [ Relation Graph ]
[ Dependency Graph ]
|
|
 Relationships |
|
Notes |
|
|
(0171657) guilleaer (viewer) 2024-11-07 19:00 |
In the case of test2, the priority is empty, so it will be treated as the first discount to apply (since no-manual discounts must be sorted by priority, and discounts with null priorities are considered first in memory). Additionally, in test2, the "Apply next discount" field is set to true, allowing the next discount, which is test1, to be applied. |
|
Notes |
|
Issue History |
|||
| Date Modified | Username | Field | Change |
| 2024-10-03 12:16 | malsasua | New Issue | |
| 2024-10-03 12:16 | malsasua | Assigned To | => Triage Platform Base |
| 2024-10-03 12:16 | malsasua | OBNetwork customer | => Gold |
| 2024-10-03 12:16 | malsasua | Triggers an Emergency Pack | => No |
| 2024-10-03 12:17 | malsasua | File Added: combo.png | |
| 2024-10-14 08:23 | malsasua | Severity | major => minor |
| 2024-10-25 11:47 | AugustoMauch | Assigned To | Triage Platform Base => Retail |
| 2024-10-29 08:15 | guilleaer | Assigned To | Retail => guilleaer |
| 2024-10-29 08:15 | guilleaer | Status | new => acknowledged |
| 2024-10-29 08:16 | Bimla_vm | Assigned To | guilleaer => Bimla_vm |
| 2024-10-29 08:16 | Bimla_vm | Status | acknowledged => scheduled |
| 2024-11-07 19:00 | guilleaer | Review Assigned To | => guilleaer |
| 2024-11-07 19:00 | guilleaer | Note Added: 0171657 | |
| 2024-11-07 19:00 | guilleaer | Status | scheduled => closed |
|
Issue History |
| Copyright © 2000 - 2009 MantisBT Group |
 |