Searches are buried when there are lots of surveys

[caharding]

Expected behaviour

When I search I need to get visual feedback that the search was performed, and easily find a way out of that search

Actual behaviour

When I have lots of surveys I can't see that results of my search, making it difficult to clear that search

Steps to reproduce the behaviour/error

Use a deployment with more than 7 surveys and you will have a problem

Recommended solution

Prepend search info above the Survey list

[brandonrosage]

I've staged a solution to this that focuses on making the "searchbar" an all-in-one tool for searching, filtering, and summarizing what filters are applied.

How it appears depends a lot on the interaction and what's being done. It listens to and reflects what the user does within the "Filters" dropdown. It can be used for text-only filtering or as a summary of what's been configured in the "Filters" dropdown.

Generally speaking, this solution moves all of the search/filter summary out of mode context and into the searchbar.

Here's a short video sample of some interaction: http://d.pr/i/1eBjY/5PAITFKZ

I intend to discuss this at the hit team in Montreal. But I'd appreciate any general feedback on the design solution, @caharding.

[caharding]

I think that this is going in a really nice direction to keep all the
contextual information about a search in the search and filter bar. It
keeps the app more consistent. I'm curious what the state would look like
after the search. Could I click an "X" on one of the filters? Also, is
there another app that does something similar we can borrow ideas from?

[rjmackay]

@brandonrosage in general I really like this direction.
One thing I think we'll need to be successful in building this is a super detailed list of the various states. ie. Given "How it appears depends a lot on the interaction and what's being done" the dev building it needs to know all the possible permutations of that and what other components its interacting with so they can build it cleanly.

We discussed a minimal vs full version of this in Montreal. Even with the minimal version it'd be useful to enumerate the states (and possible which states we're NOT building in v1)

[rjmackay]

All that said: maybe @jshorland should make a call on priority for this, in case it should really move to backlog rather than forward to design and spec

[brandonrosage]

Let's table the "smart input" solution for another day and another issue. In the interest of improving on this issue, let's do what @caharding suggested: Prepend search info above the survey filter.

[rjmackay]

@jshorland not sure what to do with the 'smart input' part of this. Send it back to backlog?

[jshorland]

issue should have been closed months ago. Sorry folks.