Project:
View Issue Details[ Jump to Notes ] | [ Issue History ] [ Print ] | |||||||
ID | ||||||||
0051751 | ||||||||
Type | Category | Severity | Reproducibility | Date Submitted | Last Update | |||
defect | [Retail Modules] Discounts and Promotions | major | always | 2023-03-01 18:36 | 2023-06-23 07:37 | |||
Reporter | Lcazaux | View Status | public | |||||
Assigned To | sreehari | |||||||
Priority | high | Resolution | fixed | 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 | 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 | 0051751: Error message when not applying a rule with a maximum quantity | |||||||
Description | 1/ In discount&promo, when entering a “max quantity”, and when the field “Apply to products up to the max quantity” = N → error message saying it is mandatory to check it and apply a rule. 2/ The phrase “Apply to products up to the maximum quantity” could be confusing since it works in reverse. For now: “Apply to products up to the maximum quantity” = Y → applies the discount even if it exceeds the maximum “Apply to products up to the maximum quantity” = N → does not apply the discount at all if it exceeds the maximum | |||||||
Steps To Reproduce | - Go to backoffice - create a new record in Discount&Promo - Configure a Price adjustment type normaly and enter a "max quantity" - Save without checking the “Apply to products up to the maximum quantity” box --> error message | |||||||
Proposed Solution | 1/ It should be possible to have this field to =N when entering a max quantity 2/ A clearer field could be used to avoid any confusion with this type of configuration. | |||||||
Tags | FASH | |||||||
Attached Files | ||||||||
![]() |
||||||||
|
![]() |
|
(0149968) hgbot (developer) 2023-05-19 11:00 |
Merge Request created: https://gitlab.com/openbravo/product/openbravo/-/merge_requests/887 [^] |
(0151532) hgbot (developer) 2023-06-23 07:37 |
Directly closing issue as related merge request is already approved. Repository: https://gitlab.com/openbravo/product/openbravo [^] Changeset: 996d1f7c4c8be1025b1c7644c72dfee3645790c2 Author: Sreehari Venkataraman <sreehari@qualiantech.com> Date: 22-06-2023 09:18:19 URL: https://gitlab.com/openbravo/product/openbravo/-/commit/996d1f7c4c8be1025b1c7644c72dfee3645790c2 [^] Fixes ISSUE-51751: Added Apply to product condition --- M src/org/openbravo/event/PriceAdjustmentHandler.java --- |
(0151533) hgbot (developer) 2023-06-23 07:37 |
Merge request merged: https://gitlab.com/openbravo/product/openbravo/-/merge_requests/887 [^] |
![]() |
|||
Date Modified | Username | Field | Change |
2023-03-01 18:36 | Lcazaux | New Issue | |
2023-03-01 18:36 | Lcazaux | Assigned To | => Retail |
2023-03-01 18:36 | Lcazaux | OBNetwork customer | => Gold |
2023-03-01 18:36 | Lcazaux | Triggers an Emergency Pack | => No |
2023-03-01 18:36 | Lcazaux | Tag Attached: FASH | |
2023-05-17 11:33 | sreehari | Assigned To | Retail => sreehari |
2023-05-17 11:33 | sreehari | Status | new => scheduled |
2023-05-19 11:00 | hgbot | Merge Request Status | => open |
2023-05-19 11:00 | hgbot | Note Added: 0149968 | |
2023-06-23 07:37 | hgbot | Merge Request Status | open => approved |
2023-06-23 07:37 | hgbot | Resolution | open => fixed |
2023-06-23 07:37 | hgbot | Status | scheduled => closed |
2023-06-23 07:37 | hgbot | Fixed in Version | => PR23Q3 |
2023-06-23 07:37 | hgbot | Note Added: 0151532 | |
2023-06-23 07:37 | hgbot | Note Added: 0151533 | |
2023-06-26 08:42 | guillermogil | Relationship added | has duplicate 0052773 |
Copyright © 2000 - 2009 MantisBT Group |