mirror of
https://github.com/qbittorrent/qBittorrent.git
synced 2026-03-02 22:57:32 -05:00
Preserve search tab search terms and filter strings across closing and opening QBT #17345
Labels
No labels
Accessibility
AppImage
Bounty
Build system
CI
Can't reproduce
Code cleanup
Confirmed bug
Confirmed bug
Core
Crash
Data loss
Discussion
Docker
Documentation
Duplicate
Feature
Feature request
Feature request
Feature request
Filters
Flatpak
GUI
Has workaround
I2P
Invalid
Libtorrent
Look and feel
Meta
NSIS
Network
Not an issue
OS: *BSD
OS: Linux
OS: Windows
OS: macOS
PPA
Performance
Project management
Proxy/VPN
Qt bugs
Qt6 compat
RSS
Search engine
Security
Temp folder
Themes
Translations
Triggers
Waiting diagnosis
Waiting info
Waiting upstream
Waiting web implementation
Watched folders
WebAPI
WebUI
autoCloseOldIssue
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/qBittorrent#17345
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @Sophist-UK on GitHub (Dec 3, 2025).
Suggestion
Sometimes I leave search tabs open (e.g. for a weekly vlog) so that I can refresh it and find the latest episode.
But if I have to reboot my computer, I lose the list of search tabs.
I would like QBT to save the search terms and filter strings for all open search tabs when you close it, and restore them (with or without an immediate refresh) the next time you open QBT.
Use case
No response
Extra info/examples/attachments
No response
@Sophist-UK commented on GitHub (Dec 3, 2025):
To clarify what I think should be saved:
Also to clarify that this feature request is different to (and complementary to) #23569 - the use case for #23569 is for the user to be able to manually save and restore sets of search tabs, whilst the use case for this one is to persist open search tabs across closing and reopening QBT. They do have some commonality, but the devs can choose to implement either one or both or neither.