mirror of
https://github.com/qbittorrent/qBittorrent.git
synced 2026-03-02 22:57:32 -05:00
Extend usefulness of labels #3080
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#3080
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 @Lycerion on GitHub (Sep 15, 2015).
Custom settings per label
Ability to set ratio limits, paths, ect
Autolabel torrents based on matching data
Full name, strings, tracker, ect
This could also be incorporated with sublabels/categories from issue #13; lowest level taking precedence on settings, with each level above carrying through if the level below isn't set.
@ghost commented on GitHub (Jun 22, 2016):
+1 specially for 1, asked for it a long time ago, it would make qbittorrent great in terms of management.
@NokTham commented on GitHub (Jun 3, 2017):
Oh I've asked for this a long time ago, it was a straight no, because apparently it's not useful for the majority of people....
+1
@thalieht commented on GitHub (Jun 4, 2017):
PR #5222 implements the things from 1. but it's abandoned for over a year.
@thalieht commented on GitHub (Feb 13, 2024):
One request per issue and there are dedicated issues for 1 and 2.