Anonymous | Login
News | My View | View Issues | Roadmap | Summary

View Issue DetailsJump to Notes ] Issue History ] Print ]
TypeCategorySeverityReproducibilityDate SubmittedLast Update
feature request[POS2] POSmajoralways2023-11-21 15:402024-04-05 13:21
ReportermhasegawaView Statuspublic 
Assigned ToRajesh_18 
PriorityurgentResolutionopenFixed in Version
StatusnewFix in branchFixed in SCM revision
ProjectionnoneETAnoneTarget Version
OSAnyDatabaseAnyJava version
OS VersionDatabase versionAnt version
Product VersionSCM revision 
Review Assigned To
Regression level
Regression date
Regression introduced in release
Regression introduced by commit
Triggers an Emergency PackNo

0053990: Search bar doesn't filter products by selected schema

DescriptionWhen searching for products using the search bar, it is possible to receive results that do not belong to the selected schema.

In such cases, the user can still add the resulting products to the order under the selected schema, even if they belong to a different schema.
Steps To Reproduce- In Livebuilds in POS2 with modules.
- With the "store" schema selected search for "cheese" (or any product not belonging to the store schema).
- Notice how the results are "cheese cake" and "cheeseburgers" (products that don't belong to the "store "schema)".
- Go from search to browse.
- Add the "cheese cake" product to the order.
- Change the schema to "restaurant".
- Notice how the "cheese cake" product retains the label of the "store" schema.
Proposed Solution- The selected schema must function as a filter during searches. This ensures that when users search for a product, they only receive results for products associated with the selected schema.
- If the user changes the schema after performing a product search, the results should be refreshed accordingly.
TagsNo tags attached.
Attached Filespng file icon Captura de pantalla 2023-11-21 150811.png [^] (106,013 bytes) 2023-11-21 15:40

- Relationships Relation Graph ] Dependency Graph ]

-  Notes
guilleaer (manager)
2024-04-05 13:21

Moved to feature request because it was decided that search does not check the active schema

- Issue History
Date Modified Username Field Change
2023-11-21 15:40 mhasegawa New Issue
2023-11-21 15:40 mhasegawa Assigned To => Retail
2023-11-21 15:40 mhasegawa File Added: Captura de pantalla 2023-11-21 150811.png
2023-11-21 15:40 mhasegawa Triggers an Emergency Pack => No
2023-11-21 15:55 mhasegawa Issue Monitored: mhasegawa
2023-11-21 15:55 mhasegawa Issue End Monitor: mhasegawa
2023-11-21 17:45 mhasegawa Steps to Reproduce Updated View Revisions
2023-11-21 17:45 mhasegawa Proposed Solution updated
2023-11-21 17:56 mhasegawa Steps to Reproduce Updated View Revisions
2023-11-21 17:56 mhasegawa Proposed Solution updated
2023-11-22 08:41 mhasegawa Proposed Solution updated
2023-11-27 11:35 SABARINATH P Assigned To Retail => SABARINATH P
2023-12-01 09:45 SABARINATH P Assigned To SABARINATH P => Rajesh_18
2024-04-05 13:21 guilleaer Type defect => feature request
2024-04-05 13:21 guilleaer Note Added: 0162889

Copyright © 2000 - 2009 MantisBT Group
Powered by Mantis Bugtracker