starred/qBittorrent

Fork 0

mirror of https://github.com/qbittorrent/qBittorrent.git synced 2026-03-02 22:57:32 -05:00

"Auto Fill" Search field option. #7697

New issue

Open

opened 2026-02-21 19:07:22 -05:00 by deekerman · 8 comments

deekerman commented

2026-02-21 19:07:22 -05:00

Owner

Originally created by @CainStar on GitHub (Sep 4, 2018).

Add an option to drop down list, when you right click on a torrent on your transfer list, to start a search in qbittorrents search engine using that torrents name. This would be much faster than copying the torrents name, and pasting it to the search field manually, and would make searching for more sources for the torrent much faster.

Originally created by @CainStar on GitHub (Sep 4, 2018). Add an option to drop down list, when you right click on a torrent on your transfer list, to start a search in qbittorrents search engine using that torrents name. This would be much faster than copying the torrents name, and pasting it to the search field manually, and would make searching for more sources for the torrent much faster.

deekerman added the

Feature request

Search engine

labels

2026-02-21 19:07:22 -05:00

deekerman commented

2026-02-21 19:07:26 -05:00

Author

Owner

@thalieht commented on GitHub (Sep 4, 2018):

This sounds very specialized to your needs, so useless for the majority of users, therefore bloat. If you download several torrents with same name from the search engine, well... stop closing the tab for that search until satisfied.

@thalieht commented on GitHub (Sep 4, 2018): This sounds very specialized to your needs, so useless for the majority of users, therefore bloat. If you download several torrents with same name from the search engine, well... stop closing the tab for that search until satisfied.

deekerman commented

2026-02-21 19:07:27 -05:00

Author

Owner

@CainStar commented on GitHub (Sep 4, 2018):

Specialized.......I want to add SOURCES, meaning other trackers to a specific torrent which might have more seeders than my original source tracker. I don't add different versios of a torrent to my download list. And the reason why I want this feature is simple, I have over 200 torrents on my download list, and lot of them have very few seeders, so the search function comes in handy when I'm looking for more seeders.

@CainStar commented on GitHub (Sep 4, 2018): Specialized.......I want to add SOURCES, meaning other trackers to a specific torrent which might have more seeders than my original source tracker. I don't add different versios of a torrent to my download list. And the reason why I want this feature is simple, I have over 200 torrents on my download list, and lot of them have very few seeders, so the search function comes in handy when I'm looking for more seeders.

deekerman commented

2026-02-21 19:07:27 -05:00

Author

Owner

@thalieht commented on GitHub (Sep 4, 2018):

Maybe adding these or some of these https://github.com/ngosang/trackerslist to your torrents might be less troublesome than searching by name which doesn't guarantee it will be the same torrent.

@thalieht commented on GitHub (Sep 4, 2018): Maybe adding these or some of these https://github.com/ngosang/trackerslist to your torrents might be less troublesome than searching by name which doesn't guarantee it will be the same torrent.

deekerman commented

2026-02-21 19:07:27 -05:00

Author

Owner

@Supralateral commented on GitHub (Sep 4, 2018):

Also ensure DHT & PEX are activated... generally these will be more than adequate at finding available peers. Searching for the exact same torrentname string sounds really ineffective

@Supralateral commented on GitHub (Sep 4, 2018): Also ensure DHT & PEX are activated... generally these will be more than adequate at finding available peers. Searching for the exact same torrentname string sounds really ineffective

deekerman commented

2026-02-21 19:07:27 -05:00

Author

Owner

@CainStar commented on GitHub (Sep 5, 2018):

thalieht - Not a bad idea, but again I have over 200 torrents on my download list, and I am not manually editing/adding new trackers to all of them. I did find an interesting thread about another feature that might help with this, but it has not been implemented yet. https://github.com/qbittorrent/qBittorrent/issues/2428

@CainStar commented on GitHub (Sep 5, 2018): thalieht - Not a bad idea, but again I have over 200 torrents on my download list, and I am not manually editing/adding new trackers to all of them. I did find an interesting thread about another feature that might help with this, but it has not been implemented yet. https://github.com/qbittorrent/qBittorrent/issues/2428

deekerman commented

2026-02-21 19:07:27 -05:00

Author

Owner

@thalieht commented on GitHub (Sep 6, 2018):

Yes it's a shame qBt doesn't have such a fundamental feature. Someone tried to make something (mentioned in that issue) but it got stuck in GUI implementation details (no one has a good idea how to present it in GUI and i think the main devs don't care about it enough but if there was a solid design idea someone might pick it up).

@thalieht commented on GitHub (Sep 6, 2018): Yes it's a shame qBt doesn't have such a fundamental feature. Someone tried to make something (mentioned in that issue) but it got stuck in GUI implementation details (no one has a good idea how to present it in GUI and i think the main devs don't care about it enough but if there was a solid design idea someone might pick it up).

deekerman commented

2026-02-21 19:07:27 -05:00

Author

Owner

@ngosang commented on GitHub (Sep 16, 2018):

Related to #167

@ngosang commented on GitHub (Sep 16, 2018): Related to #167

deekerman commented

2026-02-21 19:07:27 -05:00

Author

Owner

@xavier2k6 commented on GitHub (May 23, 2025):

ANNOUNCEMENT!

For anybody coming across this "Feature Request" & would like/love to see a potential implementation in the future!
Here are some options available to you:

Please select/click the 👍 &/or ❤ reactions in the original/opening post of this ticket.
Please feel free (If you have the "skillset") to create a "Pull Request" implementing what's being requested in this ticket.
(new/existing contributors/developers are always welcome)

DO:

Provide constructive feedback.
Display how other projects implemented same/similar etc.

DO NOT:

Add a "Bump", "me too", "2nd/3rd" etc. or "criticizing" comment(s).
(These will be disregarded/hidden as "spam/abuse/off-topic" etc. as they don't provide anything constructive.)

@xavier2k6 commented on GitHub (May 23, 2025): ## ANNOUNCEMENT! For anybody coming across this **_"Feature Request"_** & would like/love to see a potential implementation in the future! **Here are some options available to you:** 1. Please select/click the 👍 **&/or** ❤ `reactions` in the original/opening post of this ticket. 2. Please feel free _(If you have the "skillset")_ to create a **_"Pull Request"_** implementing what's being requested in this ticket. **_(new/existing contributors/developers are always welcome)_** ____ **DO:** * Provide constructive feedback. * Display how other projects implemented same/similar etc. **DO NOT:** * Add a "Bump", "me too", "2nd/3rd" etc. or "criticizing" comment(s). **(These will be disregarded/hidden as "spam/abuse/off-topic" etc. as they don't provide anything constructive.)**