Project:
View Issue Details[ Jump to Notes ] | [ Issue History ] [ Print ] | |||||||
ID | ||||||||
0055282 | ||||||||
Type | Category | Severity | Reproducibility | Date Submitted | Last Update | |||
defect | [POS2] POS | minor | always | 2024-04-22 16:15 | 2024-04-25 11:20 | |||
Reporter | Lcazaux | View Status | public | |||||
Assigned To | guilleaer | |||||||
Priority | normal | Resolution | fixed | Fixed in Version | 24Q3 | |||
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 | ||||||||
Regression level | ||||||||
Regression date | ||||||||
Regression introduced in release | ||||||||
Regression introduced by commit | ||||||||
Triggers an Emergency Pack | No | |||||||
Summary | 0055282: Bug in search of client with both name & ID number | |||||||
Description | If I search a client putting both a name (that can be applied to various customer files) + an exact loyalty member --> the search takes into account the incomplete name so it displays various records instead of just taking into account the precise loyalty member (that corresponds to only 1 customer file) See video: https://drive.google.com/file/d/1J3W7pPN0E1-snkxvyHju0qmUYYWL8pXX/view?usp=drive_link [^] | |||||||
Steps To Reproduce | ****Configuration in BO: 1- Activate the search by loyalty number via window "Enterprise Module Management", data set: Loyalty_Properties_for_the_Openbravo_Customers_CRM_Connector for Organization "*" 2- “Enable Loyalty Features” and “Allow Loyalty Category Changes” = Yes in window Channel Touchpoint Type 3- Configure a Loyalty Program: A) Configure the header with the info you want (doesnt matter) B) Configure 2 Categories in the subtab "VIP" and "Standard" for example ("approval required" MUST be at "NO" for both categories) C) Configure a status in the subtab "active" D) Add 1 customer (=business partner) in the tab "Subscription" and put 1 category and 1 status ***IN THE POS Search a client by his loyalty number (bug also is present when looking by Card ID) Click search Good client is assigned to the ticket → OK Go back to the search Keep the loyalty number (or the card ID) Put a name, in the field “Name”, that could be corresponding to various client files (example: “test”, in Dev, there are various) Search The list of all the client’s files containing “test” will appear instead of taking the precise loyalty number also indicated in the search window → KO as the search filter should take into account the loyalty number AND the name wich should lead to finding the only client that corresponds | |||||||
Proposed Solution | should take into account the loyalty number that only corresponds to 1 client | |||||||
Tags | No tags attached. | |||||||
Attached Files | ||||||||
Relationships [ Relation Graph ] [ Dependency Graph ] | |
Notes | |
(0163616) hgbot (developer) 2024-04-23 17:08 |
Merge Request created: https://gitlab.com/openbravo/product/pmods/org.openbravo.pos2/-/merge_requests/2592 [^] |
(0163730) hgbot (developer) 2024-04-25 11:20 |
Directly closing issue as related merge request is already approved. Repository: https://gitlab.com/openbravo/product/pmods/org.openbravo.pos2 [^] Changeset: 1b2be619b177df970a8cf8fd28cd21791b064321 Author: Guillermo Alvarez de Eulate <guillermo.alvarez@openbravo.com> Date: 25-04-2024 09:20:14 URL: https://gitlab.com/openbravo/product/pmods/org.openbravo.pos2/-/commit/1b2be619b177df970a8cf8fd28cd21791b064321 [^] Fixed ISSUE-55282: Use pre-filters in openbravo crm connector to narrow the search of customers --- M web-jspack/org.openbravo.pos2/src/services/crm/OBCRMUtils.js M web-jspack/org.openbravo.pos2/src/services/crm/__test__/OBCRMUtils.test.js --- |
(0163731) hgbot (developer) 2024-04-25 11:20 |
Merge request merged: https://gitlab.com/openbravo/product/pmods/org.openbravo.pos2/-/merge_requests/2592 [^] |
Issue History | |||
Date Modified | Username | Field | Change |
2024-04-22 16:15 | Lcazaux | New Issue | |
2024-04-22 16:15 | Lcazaux | Assigned To | => Retail |
2024-04-22 16:15 | Lcazaux | Triggers an Emergency Pack | => No |
2024-04-23 09:18 | guilleaer | Status | new => acknowledged |
2024-04-23 11:08 | guilleaer | Assigned To | Retail => guilleaer |
2024-04-23 11:18 | Lcazaux | Steps to Reproduce Updated | View Revisions |
2024-04-23 17:08 | hgbot | Note Added: 0163616 | |
2024-04-23 17:18 | guilleaer | Status | acknowledged => scheduled |
2024-04-25 11:20 | hgbot | Resolution | open => fixed |
2024-04-25 11:20 | hgbot | Status | scheduled => closed |
2024-04-25 11:20 | hgbot | Fixed in Version | => 24Q3 |
2024-04-25 11:20 | hgbot | Note Added: 0163730 | |
2024-04-25 11:20 | hgbot | Note Added: 0163731 |
Copyright © 2000 - 2009 MantisBT Group |