Yes, as a newer user, I’m finding it irritating to it always defaulting to the current month. If I’m searching transactions it very rare that I’m searching contractions in the current month as I can just control+F for finding that one, and I usually want to search in the last 12 or 24 months even all time, so having those as default search periods would be a great low hanging fruit UX improvement.

yeah. often I'm trying to search for things over multiple months so I can keep track of things. For example, did I get charged once and only once by a certain merchant every month. Or how many amazon transactions did I have and what were they, or a specific amount I'm searching for somewhere. The default of just searching the current month is useless and causes many more clicks every time.

Also related: https://feedback.lunchmoney.app/transactions/p/quick-search-should-not-disappear-when-a-different-date-range-is-selected

The Quick Search currently works automatically while you type, and filters transactions on the front-end: there are network queries when you filter by typing in the search box.

I would actually prefer the following behavior:

* Automatic filtering while you type: seamlessly apply search filtering based on the currently selected time range. Current behavior, no change.

* Also allow "explicit submit" of a search query (a small submit button on the right of the box + enter hotkey). The explicit submit should forcefully switch to All Time view [as per this original suggestion in this thread], while refreshing the transaction table to via /transactions?search[] endpoint; Which is the same behavior that currently happens when you change the time range manually. But saves a click.

Potentially (long-term), the full back-end search (transactions?search[]=) may leverage a stronger or more flexible searching algorithm then simple front-end filtering. This visual cue (a "submit" button + hotkey) as proposed above will further highlight this difference to the user.