mirror of
https://github.com/qbittorrent/qBittorrent.git
synced 2026-03-02 22:57:32 -05:00
Configurable "Drop-down list" when adding torrents #3580
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#3580
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 @Snurre86 on GitHub (Dec 16, 2015).
When you have "add torrent dialog" selected in options. This "Save as" and "Label" drop-down list will become unbearably messy after some use.
It would be good to have a way to manage/tidy up the suggested paths in this drop-down lists. This is only for the "add torrent dialog" not removing existing labels under "Transfers" tab.
I would suggest a way to delete each suggested path by putting a X at the right of all of them.

Making a graphical user interface for changing "[TorrentAdditionDlg]" and [TransferListFilters] in qBittorrent.ini
@chrishirst commented on GitHub (Dec 20, 2015):
#4084
#4114
#3495
@Snurre86 commented on GitHub (Dec 21, 2015):
#1082
@armandojrod commented on GitHub (Apr 12, 2016):
Also with this, remove the 10 paths limit in the drop down
@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 ❤
reactionsin 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:
DO NOT:
(These will be disregarded/hidden as "spam/abuse/off-topic" etc. as they don't provide anything constructive.)