mirror of
https://github.com/qbittorrent/qBittorrent.git
synced 2026-03-02 22:57:32 -05:00
Sub labels. #911
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#911
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 @Spork-Schivago on GitHub (Nov 10, 2013).
I would like to see an option for sub labels. For example, I have a label called ISOs and one called Movies. I would like to be able to add the Movies label to the ISO label and vice versa so ISO is a sub label under Movies. Thank you for all your hard work.
@Kervius commented on GitHub (Nov 10, 2013):
You basically ask for hierarchically organized labels. Instead of list of labels, a tree of labels.
P.S. I thought it about myself. But I personally would prefer tagging, not labeling. Main difference is that an entity (in that case a torrent/download) can have several tags. While label can be only one. With the tags one can then introduce a search/filter for the tags, and as consequence, filter of the torrents by the matching tags. That would allow to establish a loose hierarchy. But the looseness allows to jump through levels of hierarchy.
@Belove0 commented on GitHub (Nov 11, 2013):
"Tags" and "labels" are sometimes words used interchangeably; and are rarely hierarchical...
Now, I think in Utopia, labels or tags would support hierarchy but still have the feature where you can have multiple labels/tags assigned to each torrent.
This way, when you Assign the label "(in Spork-Schivago's example) "Movies" you implicitly assign Spork's label "ISO" as well. This opens up many more filtering possibilities.
For example, in a contact management application I use, there is a loose labeling scheme. I have labels for "Businesses", "Friends", "Family,", "Government", "NGOs", etc. I also have labels for specific cooperative groups of people I interact with on different subjects an teams of people within organizations. Then, I have labels for geographic region. Just taking the geographic region as an example, I have created labels such as "Africa" "West Africa" and "Cameroon". That is great, and I can assign all three labels to every contact in Cameroon, enabling me to filter by broad or narrow region, but this is tedious and error-prone. Especially since the same contact is also labeled in various other contexts besides region where I must do the same thing.
So, I would argue that labels are much more useful than a strict folder/directory-only filing scheme, but they can be given the same features and we can have the best of both worlds.
Some people achieve a compromise where they create labels such as "Africa/West Africa/Cameroon". That solves a sorting of labels issue; but it does not allow to filter for West Africa or Africa without filtering for a specific country.
So, in short, I think this is a good and useful proposal, but not instead of allowing multiple labels :)
@JinxDojo commented on GitHub (Jan 6, 2014):
Multiple labels/tagging is what we need: https://github.com/qbittorrent/qBittorrent/issues/13
@alfrix commented on GitHub (Feb 8, 2014):
@sledgehammer999 dupe of #13