Page MenuHomePhabricator

Search Satisfaction eventlogging doesn't include input location with click events
Closed, DeclinedPublic

Description

It would be convenient to grab click events from particular input boxes, but all the events we record have a null for inputLocation which prevents differentiating them. User behaviour certainly varies between the header and Special:Search autocompletes so evaluating them separately will be useful.

Doesn't seem strictly necessary yet, but would be good to fix.

Event Timeline

EBernhardson moved this task from needs triage to Tech Debt/Misc on the Discovery-Search board.
MPhamWMF subscribed.

Closing out low/est priority tasks over 6 months old with no activity within last 6 months in order to clean out the backlog of tickets we will not be addressing in the near term. Please feel free to reopen if you think a ticket is important, but bare in mind that given current priorities and resourcing, it is unlikely for the Search team to pick up these tasks for the indefinite future. We hope that the requested changes have either been addressed by or made irrelevant by work the team has done or is doing -- e.g. upgrading Elasticsearch to a newer version will solve various ES-related problems -- or will be subsumed by future work in a more generalized way.

RhinosF1 removed a project: Discovery-Search.
RhinosF1 subscribed.

Re-opening tasks and removing from team workboard per IRC feedback given yesterday and discussion with MPham.

Gehel subscribed.

Specific fixes to search data collection doesn't really make sense at this point. We need to have a more systemic approach to eventlogging instead.