starred/qBittorrent

Fork 0

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

Torrent Queue and/or priority #2492

New issue

Open

opened 2026-02-21 16:14:58 -05:00 by deekerman · 7 comments

deekerman commented

2026-02-21 16:14:58 -05:00

Owner

Originally created by @ambroisie on GitHub (May 15, 2015).

As we can already set a priority for files downloaded in a torrent, could we also have a priority system or a queue that would allow to let one or more torrent get priority over the available bandwith jst like µTorrent allows us to do with the queue and the priority sysem they implemented ?

Originally created by @ambroisie on GitHub (May 15, 2015). As we can already set a priority for files downloaded in a torrent, could we also have a priority system or a queue that would allow to let one or more torrent get priority over the available bandwith jst like µTorrent allows us to do with the queue and the priority sysem they implemented ?

deekerman added the

Feature request

label

2026-02-21 16:14:58 -05:00

deekerman commented

2026-02-21 16:15:02 -05:00

Author

Owner

@ngosang commented on GitHub (May 15, 2015):

Tools => Options => BitTorrent Tab => Torrent Queuing

@ngosang commented on GitHub (May 15, 2015): Tools => Options => BitTorrent Tab => Torrent Queuing

deekerman commented

2026-02-21 16:15:02 -05:00

Author

Owner

@ambroisie commented on GitHub (May 16, 2015):

Well unfortunately I am looking after a different option from what you're telling me. This option panel onlu allows us to restrict the number of active torrents, I'm looking after the same feature that's possible in µTorrent, which is directly found in the right clik menu. You can choose easily what torrent should be prioritised, directly from this context menu.

Thanks anyways if you don't have it as a current feature, but I'd really like to see it become one.

@ambroisie commented on GitHub (May 16, 2015): Well unfortunately I am looking after a different option from what you're telling me. This option panel onlu allows us to restrict the number of active torrents, I'm looking after the same feature that's possible in µTorrent, which is directly found in the right clik menu. You can choose easily what torrent should be prioritised, directly from this context menu. Thanks anyways if you don't have it as a current feature, but I'd really like to see it become one.

deekerman commented

2026-02-21 16:15:02 -05:00

Author

Owner

@ngosang commented on GitHub (May 16, 2015):

Sorry, we don't have this feature at this moment. Add the word [Wishlist] in the title.

@ngosang commented on GitHub (May 16, 2015): Sorry, we don't have this feature at this moment. Add the word [Wishlist] in the title.

deekerman commented

2026-02-21 16:15:02 -05:00

Author

Owner

@ambroisie commented on GitHub (May 16, 2015):

Okay thanks, I'm looking forward to it, keep up the good work !

@ambroisie commented on GitHub (May 16, 2015): Okay thanks, I'm looking forward to it, keep up the good work !

deekerman commented

2026-02-21 16:15:02 -05:00

Author

Owner

@ngosang commented on GitHub (May 17, 2015):

Related in someway #2825.

@ngosang commented on GitHub (May 17, 2015): Related in someway #2825.

deekerman commented

2026-02-21 16:15:02 -05:00

Author

Owner

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

Duplicate of #566?

@thalieht commented on GitHub (Sep 18, 2018): Duplicate of #566?

deekerman commented

2026-02-21 16:15:03 -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.)**