mirror of
https://github.com/qbittorrent/qBittorrent.git
synced 2026-03-02 22:57:32 -05:00
Automated RSS downloader Priority assigning #3338
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#3338
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 @BIG-FAN on GitHub (Nov 15, 2015).
Add an option in the Automated RSS downloader to assign priority to the torrents (when i say assign priority it is to the downloaded torrent file)
eg: Maximum active downloads/torrents = 1 (this is just my personal settings cus my internet speed sux)
torrent 'A' get released at 7.00 pm (ETA 2.30 hours to fully download)
torrent 'B' get released at 8.00 pm <------ set to top priority when available(or custom priority number)
@Xesucrist0 commented on GitHub (Jan 20, 2017):
I'd like to see that in the future!
@4luk commented on GitHub (Nov 25, 2018):
Yes please this would be great
@diamant-x commented on GitHub (Jan 27, 2021):
Other use cases, wich might benefit from this feature request, or different implementation.
(if found in list #1 then add first there to the downloader, then if found in the list #2, add it in second place after adding the source from #1). That way it might get downloaded from the first list and cross-seeded in the second one.
@luzpaz commented on GitHub (Oct 19, 2022):
Related to #4793 and #5831
@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.)