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

View Issue DetailsJump to Notes ] Issue History ] Print ]
ID
0044258
TypeCategorySeverityReproducibilityDate SubmittedLast Update
feature request[Retail Modules] Web POSmajorhave not tried2020-06-02 09:402020-06-02 09:40
ReporterioritzCiaView Statuspublic 
Assigned ToRetail 
PrioritynormalResolutionopenFixed in Version
StatusnewFix in branchFixed in SCM revision
ProjectionnoneETAnoneTarget Version
OSLinux 64 bitDatabasePostgreSQLJava version8
OS VersionUbuntu 18.04Database version11Ant version1.9
Product VersionSCM revision 
Review Assigned To
Regression level
Regression date
Regression introduced in release
Regression introduced by commit
Triggers an Emergency PackNo
Summary

0044258: It should be possible to identify the origin of a POS filter

DescriptionIn order to overwrite the behavior of a POS filter like for example the product search one it should be possible to identify to which functionality do the filters belong.
Steps To ReproduceMake a search in the POS and see the filters' json. You can identify the origin by the content, but when programming, it would be quite difficult.
Proposed SolutionThe patch attached is the result of talks with retail team. It is a patch for mobile core module.
TagsNo tags attached.
Attached Filesdiff file icon fullTextSearch_mobilecore.diff [^] (734 bytes) 2020-06-02 09:40 [Show Content]

- Relationships Relation Graph ] Dependency Graph ]

-  Notes
There are no notes attached to this issue.

- Issue History
Date Modified Username Field Change
2020-06-02 09:40 ioritzCia New Issue
2020-06-02 09:40 ioritzCia Assigned To => Retail
2020-06-02 09:40 ioritzCia File Added: fullTextSearch_mobilecore.diff
2020-06-02 09:40 ioritzCia Triggers an Emergency Pack => No


Copyright © 2000 - 2009 MantisBT Group
Powered by Mantis Bugtracker