Sort downloading torrents by ETA when sorting by "Completed on" #2968

New issue

Open

opened 2026-02-21 16:30:39 -05:00 by deekerman · 2 comments

deekerman commented

2026-02-21 16:30:39 -05:00

Owner

Originally created by @UltimateByte on GitHub (Aug 20, 2015).

Hi,
I guess the title is pretty self-explanatory...
I have to say i'm pretty proud of this idea, as long as i know, no torrent program does that yet, and it would keep a quite constant sorting before and after torrent completion which would be way more convenient.

Also posted this to the forum first (thought that'd be better but then i read the pined topic) https://qbforums.shiki.hu/index.php/topic,3750.0.html

Keep up with the good work !
Cheers !

Originally created by @UltimateByte on GitHub (Aug 20, 2015). Hi, I guess the title is pretty self-explanatory... I have to say i'm pretty proud of this idea, as long as i know, no torrent program does that yet, and it would keep a quite constant sorting before and after torrent completion which would be way more convenient. Also posted this to the forum first (thought that'd be better but then i read the pined topic) https://qbforums.shiki.hu/index.php/topic,3750.0.html Keep up with the good work ! Cheers !

deekerman added the

Feature request

label

2026-02-21 16:30:39 -05:00

deekerman commented

2026-02-21 16:30:43 -05:00

Author

Owner

@shthed commented on GitHub (Apr 12, 2016):

This would be possible with #3045 Secondary sort in transfer view columns

@shthed commented on GitHub (Apr 12, 2016): This would be possible with #3045 Secondary sort in transfer view columns

deekerman commented

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