Openbravo Issue Tracking System - Retail Modules
View Issue Details
0053513Retail ModulesWeb POSpublic2023-09-21 10:042024-09-03 12:27
ngarcia 
Rajesh_18 
urgentmajoralways
scheduledopen 
5
 
 
Production - Confirmed Stable
2022-09-06
RR23Q1
https://gitlab.com/openbravo/product/pmods/org.openbravo.retail.posterminal/-/commit/b03613ff6b335f3100f53ba49e03dc511ddca4e1 [^]
No
0053513: Change payment is considered a sale and it is summed to the expected amount of the cashup when paying with Pay Open Tickets
Change payment is considered a sale and it is summed to the expected amount of the cashup when paying with Pay Open Tickets
Log in in the POS
Add Adhesive body warmers product (3.60)
Do not complete the ticket
Click on New Receipt
Add Adhesive body warmers classic product (5.00)
Do not complete the ticket
Click on Pay Open Tickets menu option
Select both receipts
Pay them with 10 euros
Check the change is shown as 1.40

Do the cashup
Check 10 is summed up to the expected amount in cash instead of 8.60 (This is wrong)

In the backoffice
Check two payments have been created with a total amount of 10 and the change amount has been split and assigned to the overpayment G/L Item. This doesn't happen if you do a change payment over a single ticket

Check the Total Sales for Cash in Channel Touchpoint - Cash Up History - Payment Method status cashup tab is 10 instead of 8.60
No tags attached.
Issue History
2023-09-21 10:04ngarciaNew Issue
2023-09-21 10:04ngarciaAssigned To => Retail
2023-09-21 10:04ngarciaTriggers an Emergency Pack => No
2023-09-21 12:07Rajesh_18Assigned ToRetail => Rajesh_18
2023-09-21 12:08Rajesh_18Statusnew => acknowledged
2023-09-21 12:08Rajesh_18Statusacknowledged => scheduled
2023-09-22 09:32Rajesh_18Regression level => Production - Confirmed Stable
2023-09-22 09:32Rajesh_18Regression date => 2022-09-06
2023-09-22 09:32Rajesh_18Regression introduced in release => RR23Q1
2023-09-22 09:32Rajesh_18Regression introduced by commit => https://gitlab.com/openbravo/product/pmods/org.openbravo.retail.posterminal/-/commit/b03613ff6b335f3100f53ba49e03dc511ddca4e1 [^]
2023-09-22 09:32Rajesh_18Statusscheduled => acknowledged
2023-09-22 09:33Rajesh_18Statusacknowledged => scheduled
2023-09-25 10:41hgbotNote Added: 0155199
2023-10-05 08:45Rajesh_18Statusscheduled => acknowledged
2023-10-05 08:45Rajesh_18Statusacknowledged => scheduled
2024-08-12 08:55hgbotNote Added: 0167946
2024-08-12 14:02marvintmStatusscheduled => acknowledged
2024-08-12 14:02marvintmStatusacknowledged => scheduled
2024-09-03 12:27marvintmNote Added: 0168692
2024-09-03 12:27marvintmTypedefect => design defect

Notes
(0155199)
hgbot   
2023-09-25 10:41   
Merge Request created: https://gitlab.com/openbravo/product/pmods/org.openbravo.retail.posterminal/-/merge_requests/1360 [^]
(0167946)
hgbot   
2024-08-12 08:55   
Merge Request created: https://gitlab.com/openbravo/ci/mobile-test/-/merge_requests/407 [^]
(0168692)
marvintm   
2024-09-03 12:27   
Finally we are changing this issue to design defect, and we are also removing the regression fields.

We don't consider it as a regression, as it is happening only in a new functionality (the configuration to set Pay Open Tickets to generate a single payment instead of individual payments), and not in existing functionality.

After discussing with Product Management, and understanding the changes that would need to be done to solve this problem, we believe it would be a small project, which doesn't fill the scope for a standard defect. This is why we are changing it to design defect.

We propose to solve this problem once the Pay Open Tickets functionality is proposed to be migrated to React.