Anonymous | Login
Project:
RSS
  
News | My View | View Issues | Roadmap | Summary

View Issue Details[ Jump to Notes ] [ Issue History ] [ Print ]
ID
0052449
TypeCategorySeverityReproducibilityDate SubmittedLast Update
backport[POS2] POSminorhave not tried2023-05-15 14:382023-05-17 10:18
ReporterjayalaView Statuspublic 
Assigned Tojayala 
PrioritynormalResolutionfixedFixed in Version23Q2.1
StatusclosedFix in branchFixed in SCM revision
ProjectionnoneETAnoneTarget Version23Q2.1
OSAnyDatabaseAnyJava version
OS VersionDatabase versionAnt version
Product VersionSCM revision 
Merge Request Statusapproved
Review Assigned To
OBNetwork customerNo
Support ticket
Regression level
Regression date
Regression introduced in release
Regression introduced by commit
Triggers an Emergency PackNo
Summary

0052449: Open ticket with correct schema

DescriptionWhen you open a ticket with a different schema or delivery mode than the terminal, the POS system should try to select it in order to display it correctly. If it cannot do so because it is not configured in the terminal, it should open it using the default schema. In either of these two cases, a small pop-up will be displayed with a warning indicating this anomaly to the user.
Steps To Reproduce1. Search for a ticket which has the field "obpos2OrgSchema" filled.
2. Open the order.
3. See that order is opened but not in the schema indicated for the order.
Proposed SolutionIt has been noticed that the current development did not take into account the deliveryModeSelection === 'A' (All) for the schema 'calculation,' so it is being added. Furthermore, the developed logic is the opposite. If deliveryModeSelection === 'I', the schema should be included, and if deliveryModeSelection === 'E', the schema should be excluded.
TagsNo tags attached.
Attached Files

- Relationships [ Relation Graph ] [ Dependency Graph ]
blocks defect 0052448 closedjayala Open ticket with correct schema 

-  Notes
(0149834)
hgbot (developer)
2023-05-16 14:57

 Merge Request created: https://gitlab.com/openbravo/product/pmods/org.openbravo.pos2/-/merge_requests/1803 [^]
(0149835)
hgbot (developer)
2023-05-16 14:58

 Merge request closed: https://gitlab.com/openbravo/product/pmods/org.openbravo.pos2/-/merge_requests/1803 [^]
(0149836)
hgbot (developer)
2023-05-16 15:03

 Merge Request created: https://gitlab.com/openbravo/product/pmods/org.openbravo.pos2/-/merge_requests/1804 [^]
(0149864)
hgbot (developer)
2023-05-17 10:18

 Directly closing issue as related merge request is already approved.

Repository: https://gitlab.com/openbravo/product/pmods/org.openbravo.pos2 [^]
Changeset: 71a11dda4883d3c8d344d74f9fdb32b97cad1722
Author: Javier Ayala <javier.ayala@openbravo.com>
Date: 16-05-2023 16:21:37
URL: https://gitlab.com/openbravo/product/pmods/org.openbravo.pos2/-/commit/71a11dda4883d3c8d344d74f9fdb32b97cad1722 [^]

Fixed ISSUE-52449: Open ticket with correct schema

---
M web-jspack/org.openbravo.pos2/src/model/ticket/__test__/SetCurrentSchema.test.js
M web-jspack/org.openbravo.pos2/src/model/ticket/actions/SetCurrentSchema.js
M web-jspack/org.openbravo.pos2/src/model/user-interface/__test__/SelectCurrentSchema.test.js
M web-jspack/org.openbravo.pos2/src/model/user-interface/user-actions/SelectCurrentSchema.js
---
(0149865)
hgbot (developer)
2023-05-17 10:18

 Merge request merged: https://gitlab.com/openbravo/product/pmods/org.openbravo.pos2/-/merge_requests/1804 [^]

- Issue History
Date Modified Username Field Change
2023-05-15 14:42 jayala Type defect => backport
2023-05-15 14:42 jayala Target Version => 23Q2.1
2023-05-16 14:57 hgbot Note Added: 0149834
2023-05-16 14:58 hgbot Note Added: 0149835
2023-05-16 15:03 hgbot Note Added: 0149836
2023-05-17 10:18 hgbot Merge Request Status open => approved
2023-05-17 10:18 hgbot Resolution open => fixed
2023-05-17 10:18 hgbot Status scheduled => closed
2023-05-17 10:18 hgbot Fixed in Version => 23Q2.1
2023-05-17 10:18 hgbot Note Added: 0149864
2023-05-17 10:18 hgbot Note Added: 0149865

Copyright © 2000 - 2009 MantisBT Group
Powered by Mantis Bugtracker