After years of use, I still always click in the BrewwQL box to search by order number before realising it’s not the search bar. It feels to me that the search bar in any list screen should be the primary input box, and BrewwQL the secondary?
Does anyone else find this frustrating? Probably just me.
Thanks for the suggestion, Simon.
If we did this, we’d suddenly annoy everyone who is used to how it currently works 
The search box also typically doesn’t need much width, whereas the BrewwQL filter box often needs the extra width.
On almost all “list pages”, with the notable exception of the customer list, you can, in fact, search using the BrewwQL box (give it a try on the order list). Breww will detect that the entry isn’t valid BrewwQL and treat it as a search instead. The customer list can’t do this because it’s built using a legacy approach that we’re gradually moving away from. Hopefully before long this list will have been moved to the new “list framework” and so this won’t be an issue.
We appreciate the feedback, but for the above reasons, this doesn’t really need to be a feature request, so I’ll close it, but rest assured at some point in the future the customer list will be updated and the main BrewwQL box will be able to work with BrewwQL or a search. Thank you.
This topic was automatically closed 5 days after the last reply. New replies are no longer allowed.