Project:
View Issue Details[ Jump to Notes ] | [ Issue History ] [ Print ] | |||||||
ID | ||||||||
0049195 | ||||||||
Type | Category | Severity | Reproducibility | Date Submitted | Last Update | |||
defect | [Retail Modules] Discounts and Promotions | major | always | 2022-05-03 14:47 | 2022-06-10 09:05 | |||
Reporter | rfacon | View Status | public | |||||
Assigned To | radhakrishnan | |||||||
Priority | normal | Resolution | no change required | 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 | |||||||
Review Assigned To | marvintm | |||||||
Regression level | ||||||||
Regression date | ||||||||
Regression introduced in release | ||||||||
Regression introduced by commit | ||||||||
Triggers an Emergency Pack | No | |||||||
Summary | 0049195: Availability subtab records can be deleted | |||||||
Description | Availability subtab records can be deleted | |||||||
Steps To Reproduce | 1. Configure a discount in the Backend, for example: - Discount/Promotion Type: Price adjustment - Active = Y - Define the discount for a product 2. Availability subtab : add a new record by indicating a day 3. Delete the record created at step 2 by selecting it and clicking on the bin icon (or by doing a right click + delete) Result : even if the record is deleted in the BO, it remains active in the POS masterdatas. To avoid this issue, we shouldn't be able to delete records of the availibility subtab, but only to put them as inactive in case they are not used | |||||||
Tags | NOR | |||||||
Attached Files | ||||||||
Relationships [ Relation Graph ] [ Dependency Graph ] | ||||||||||||||||||||||||||||||||||||
|
Notes | |
(0138238) marvintm (manager) 2022-06-10 09:05 |
Disallowing deletions in this tab would be inconsistent with the rest of the masterdata tables, where we do allow deletions, so we think this is not the right approach. It would be very confusing to not allow deletions here, and allow them in the rest of the discounts filters for example. |
Issue History | |||
Date Modified | Username | Field | Change |
2022-05-03 14:47 | rfacon | New Issue | |
2022-05-03 14:47 | rfacon | Assigned To | => Retail |
2022-05-03 14:47 | rfacon | Triggers an Emergency Pack | => No |
2022-05-04 10:28 | rafaroda | Tag Attached: NOR | |
2022-05-04 10:28 | rafaroda | Relationship added | related to 0049204 |
2022-05-04 10:28 | rafaroda | Relationship added | related to 0049194 |
2022-05-04 10:29 | rafaroda | Relationship added | related to 0048383 |
2022-05-04 10:30 | rafaroda | Type | backport => defect |
2022-06-07 21:44 | rafaroda | Issue Monitored: rafaroda | |
2022-06-08 16:09 | radhakrishnan | Assigned To | Retail => radhakrishnan |
2022-06-09 15:20 | radhakrishnan | Status | new => scheduled |
2022-06-09 23:44 | rafaroda | Relationship added | related to 0049517 |
2022-06-09 23:44 | rafaroda | Relationship added | related to 0049518 |
2022-06-10 09:05 | marvintm | Review Assigned To | => marvintm |
2022-06-10 09:05 | marvintm | Note Added: 0138238 | |
2022-06-10 09:05 | marvintm | Status | scheduled => closed |
2022-06-10 09:05 | marvintm | Resolution | open => no change required |
Copyright © 2000 - 2009 MantisBT Group |