Openbravo Issue Tracking System - Retail Modules
View Issue Details
IDProjectCategoryView StatusDate SubmittedLast Update
0027047Retail ModulesWeb POSpublic2014-07-10 21:002015-02-27 15:26
Reporterdbaz 
Assigned Tomarvintm 
PriorityurgentSeveritymajorReproducibilityalways
StatusclosedResolutionfixed 
PlatformOS5OS Version
Product Version 
Target VersionFixed in VersionRR15Q2 
Merge Request Status
Review Assigned Toadrianromero
OBNetwork customer
Support ticket
Regression level
Regression date
Regression introduced in release
Regression introduced by commit
Triggers an Emergency PackNo
Summary0027047: [UX] SEARCH component is not working properly
DescriptionThe behavior of the filters in the search component is not consistent.

The left buttons in yellow (filter of this category already applied) should be remain there always until this filter be removed.
Steps To ReproduceLogin into the webpos as "demouser"

Go to "SEARCH" panel

Tap "Price" filter button and select "20€ - 50€"
"Price" button is yellow and also remain there the following buttons:
* Brand
* Battery Life
* Capacity
* Dimension
* Material
* Object
* Range
* Size
* Use
* Weight

This is ok, because this means that there is something already applied in "Price" and you can still finetuning more the search by modifying one of the remaining filters

Tap "Material" filter button and select "Aluminium"
"Material" button is yellow and also remain there the following buttons:
* Brand
* Object
* Price (in yellow)
* Use

This is ok, because this means that there is something already applied in "Price" and "Material" you can still finetuning more the search by modifying one of the remaining filters


Tap "Object" filter button and select "Back Packs"
All the buttons except "Brand" dissapear and a new "Clear Filters" button is shown

This is wrong. The behavior here should be that "Price", "Material" and "Object" buttons in yellow should remain there (although there are no search results because no product satisfy the filters) to allow the user go back, and unselect for example the last added filter and go back to the previous state.

Also, the "Clear Filters" button should be removed, because this action can already be done by the "X" grey button in the top.
Proposed Solution
Additional Information
TagsNo tags attached.
Relationships
Attached Files
Issue History
Date ModifiedUsernameFieldChange
2014-07-10 21:00dbazNew Issue
2014-07-10 21:00dbazAssigned To => marvintm
2014-07-10 21:00dbazTriggers an Emergency Pack => No
2014-07-10 22:26dbazSummarySEARCH component is not working properly => [UX] SEARCH component is not working properly
2014-07-11 00:10dbazSteps to Reproduce Updatedbug_revision_view_page.php?rev_id=6032#r6032
2015-02-23 20:00OsmanyNote Added: 0074822
2015-02-23 20:23dbazNote Added: 0074823
2015-02-24 15:29hgbotCheckin
2015-02-24 15:29hgbotNote Added: 0074849
2015-02-24 15:29hgbotStatusnew => resolved
2015-02-24 15:29hgbotResolutionopen => fixed
2015-02-24 15:29hgbotCheckin
2015-02-24 15:29hgbotFixed in SCM revision => http://code.openbravo.com/erp/pmods/org.openbravo.mobile.core/rev/9fbe4bd927da24e1fb7677c6221724521c712bd9 [^]
2015-02-24 15:29hgbotNote Added: 0074850
2015-02-24 15:33OsmanyNote Deleted: 0074849
2015-02-27 15:26adrianromeroReview Assigned To => adrianromero
2015-02-27 15:26adrianromeroNote Added: 0075047
2015-02-27 15:26adrianromeroStatusresolved => closed
2015-02-27 15:26adrianromeroFixed in Version => RR15Q2

Notes
(0074822)
Osmany   
2015-02-23 20:00   
Hi David,

The functionality is fine(code == functionality), but you want to change the behavior? Then is new functionality.

Regards.
(0074823)
dbaz   
2015-02-23 20:23   
It depends on the definition that you give to functionality. For me functionality it is not just "code".

One possible definition of functionality is "any or all of the operations performed by a piece of equipment or a software program"

And for me in the operations or behavior of this component there is a clear UI (that no code) defect ("A shortcoming, imperfection, or lack")

If in the retail team you want to lower its priority and move it into "design defect" I am fine with that, but one thing is clear, it is not new functionality, it is bad functionality because it works ok (as expected) until you reach the case where you cannot continue filtering; in this case, an unnecessary "Clear Filters" button is shown instead of showing the applied button filters in yellow (as in previous filtering steps).

Regards.
(0074850)
hgbot   
2015-02-24 15:29   
Repository: erp/pmods/org.openbravo.mobile.core
Changeset: 9fbe4bd927da24e1fb7677c6221724521c712bd9
Author: Osmany Garcia Machado <osmany.machado <at> peoplewalking.com>
Date: Tue Feb 24 08:29:07 2015 -0600
URL: http://code.openbravo.com/erp/pmods/org.openbravo.mobile.core/rev/9fbe4bd927da24e1fb7677c6221724521c712bd9 [^]

Fixed issue 27047: [UX] SEARCH component is not working properly.

---
M web/org.openbravo.mobile.core/source/retail/component/ob-retail-searchproductcharacteristic.js
---
(0075047)
adrianromero   
2015-02-27 15:26   
Verified