flamber

Workaround is to use Custom Expression, like `contains([Name], "Wood") OR contains([Name], "Lake")` https://www.metabase.com/docs/latest/users-guide/expressions.html

It was likely created this way because of #17578 and #13960. Seems like it's difficult to keep the parameter and also know that it should be searching for empty string...

Almost a repeat of #12395. But the same thing happened on 0.41.x Likely very related to #13455 and maybe to #12044 and #18770 and #22382 Steps to reproduce: 1. Question...

@willbryant Sounds like you're seeing #24626

@willbryant This issue is a backend problem, and has a workaround. #24626 was a frontend specific problem.

@willbryant This issue has nothing to do with #24626. #24626 has been fixed and will be part of 0.44.1 as noted in the sidebar of the issue (Milestone).

@willbryant Please open a new issue if you are seeing a different problem.

It seems to be only an issue for date pickers. When trying number/string picker, then it saves on `Enter`. On the date picker, if you try to input 300 and...

@Beeskey You are likely seeing #22563, if not, then create a new issue with clear steps-to-reproduce.

@MuriloAmarals Please just create a PR if you want and think you can fix an issue. Don't leave a comment. If you cannot reproduce an issue, then don't a comment,...