"Paused" filter should lists only torrents with "Paused" status #13710

New issue

Open

opened 2026-02-22 00:14:58 -05:00 by deekerman · 2 comments

deekerman commented

2026-02-22 00:14:58 -05:00

Owner

Originally created by @tristanleboss on GitHub (Aug 10, 2022).

Suggestion

Hello,

When I used the "Paused" status filter in the GUI, I get torrents with both "Paused" status and also unexpected torrents with "Completed" status. For me, these "Completed" torrents should not be listed in this view. This view is really helpful to see the torrents that are paused because you don't want them to start downloading.

I was thinking they may be showing up because I set the torrents to "Pause torrent" (in Options > BitTorrent > Seeding Limits) once the ratio reaches 1. This "Pause torrent" label is not very clear. Indeed, it will never really change the status to "Paused" because, even if the ratio of 1 is reached before torrent completion, qBittorent will not pause it: it will wait for it to -at least- complete download. When torrent completes downloading, it gets the status of "Seeding" and, once it reaches a share ratio of 1, it gets a status of "Completed". If the share ratio of 1 is reached during download, the torrent directly get the "Completed" status once done downloading.

Use case

Being able to distinguish completed but seeding torrents from completed but prevented to seed (paused) torrents.

Extra info/examples/attachments

No response

Originally created by @tristanleboss on GitHub (Aug 10, 2022). ### Suggestion Hello, When I used the "Paused" status filter in the GUI, I get torrents with both "Paused" status and also unexpected torrents with "Completed" status. For me, these "Completed" torrents should not be listed in this view. This view is really helpful to see the torrents that are paused because you don't want them to start downloading. I was thinking they may be showing up because I set the torrents to "Pause torrent" (in Options > BitTorrent > Seeding Limits) once the ratio reaches 1. This "Pause torrent" label is not very clear. Indeed, it will never really change the status to "Paused" because, even if the ratio of 1 is reached before torrent completion, qBittorent will not pause it: it will wait for it to -at least- complete download. When torrent completes downloading, it gets the status of "Seeding" and, once it reaches a share ratio of 1, it gets a status of "Completed". If the share ratio of 1 is reached during download, the torrent directly get the "Completed" status once done downloading. ### Use case Being able to distinguish completed but seeding torrents from completed but prevented to seed (paused) torrents. ### Extra info/examples/attachments _No response_

deekerman added the

Feature request

Filters

labels

2026-02-22 00:14:58 -05:00

deekerman commented

2026-02-22 00:15:05 -05:00

Author

Owner

@AlexMhr commented on GitHub (Mar 10, 2023):

FWIW I agree, I requested a custom status filter creator here https://github.com/qbittorrent/qBittorrent/issues/18661, which I think would resolve all status filter confusion.

@AlexMhr commented on GitHub (Mar 10, 2023): FWIW I agree, I requested a custom status filter creator here [https://github.com/qbittorrent/qBittorrent/issues/18661](https://github.com/qbittorrent/qBittorrent/issues/18661), which I think would resolve all status filter confusion.

deekerman commented

2026-02-22 00:15:07 -05:00

Author

Owner

@xavier2k6 commented on GitHub (May 24, 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 24, 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.)**