Filter event tracking has a bug in Chorus.
In case a filter is set and a (new) query is entered, not only the query event is fired but also the brand filter event - although nothing has changed with the set of filters.
Steps to reproduce:
- Go to http://chorus-opensearch-edition.dev.o19s.com:3000/
- Select a filter, e.g.
Philips as a brand filter
- Open OS Dashboards in a new tab: http://chorus-opensearch-edition.dev.o19s.com:5601
- Go to Dev Tools and execute the following query:
GET ubi_events/_search
{
"query": {
"match_all": {
}
}, "sort": [
{
"timestamp": {
"order": "desc"
}
}
],
"track_total_hits": true
}
You should see the latest event, namely the clicked brand filter.
- Go to the Chrous UI tab and enter a query, e.g.
coffee
- Switch back to Dev Tools and observe multiple brand filter events although no brands were selected or deselcted.
Apparently, every query triggers a filter event if a filter already is selected.
It's also worth thinking about resetting the filters if a completely new query is entered vs. keeping the filters if the query is changed.
Filter event tracking has a bug in Chorus.
In case a filter is set and a (new) query is entered, not only the query event is fired but also the brand filter event - although nothing has changed with the set of filters.
Steps to reproduce:
Philipsas a brand filterYou should see the latest event, namely the clicked brand filter.
coffeeApparently, every query triggers a filter event if a filter already is selected.
It's also worth thinking about resetting the filters if a completely new query is entered vs. keeping the filters if the query is changed.