Feature: Remember search filters between searches (option) - #24696
Open
rorybot wants to merge 3 commits into
Open
Feature: Remember search filters between searches (option)#24696rorybot wants to merge 3 commits into
rorybot wants to merge 3 commits into
Conversation
The search filter row lets you narrow results by minimum/maximum seeds and size, but those values reset to their defaults with every new search tab, so recurring filters (e.g. "at least 5 seeds") have to be re-entered each time. Add a "Remember filters" checkbox to the search filter row. When ticked, the current seeds and size filter values (including size units) are saved and pre-filled into every new search tab; when unticked, behaviour is unchanged. The stored values and the checkbox state persist across sessions, following the same SettingValue pattern already used for the "Search in" name-filtering mode. Closes qbittorrent#8042 Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_015FE31f3czMACwmRDUFchDM
Mirror the desktop GUI "Remember filters" feature in the Web interface. Previously the seeds and size search filters reset to their defaults for every new search tab (resetFilters()), while only the "Search in" mode persisted via ClientData. Add a "Remember filters" checkbox to the search filter row. When ticked, the seeds/size filter values (including size units) are stored via ClientData and used to seed new search tabs; when unticked, behaviour is unchanged. The stored values and checkbox state persist across sessions, following the same ClientData pattern already used for "search_in_filter". Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_015FE31f3czMACwmRDUFchDM
The min/max size unit dropdowns were wired to a short-circuiting handler that skipped saving whenever both size inputs were 0, causing the unit to silently revert on tab switch or reload when "Remember filters" was enabled. Wire them to searchSizeFilterChanged directly, matching the Qt widget's behavior.
rorybot
force-pushed
the
feature/remember-search-filters
branch
from
July 16, 2026 01:38
35dace8 to
27ddb22
Compare
rorybot
marked this pull request as ready for review
July 16, 2026 01:39
rorybot
changed the title
rorybot
changed the title
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
👀
😲
Resolves: #8042 / #20212... this has been requested as far back as #2559 and its lack of implementation by anyone annoyed me!
Description
Adds an opt-in "Remember filters" checkbox to the Search tab (both the Qt GUI and WebUI). When enabled, the seeds and size filter values (and their units) are persisted and restored on new searches, instead of always resetting to the hardcoded defaults.
SearchJobWidget, backed bySettingValue-stored filter values.search_remember_filters,search_min_seeds, etc.).Test plan
Misc
Happy to take a steer on styling, placement, etc. Some people may want per-filter remembering, rather than all of them, but I think this solves 80% of cases. It does for me at least.