Do not automatically move previously completed torrent to the incomplete folder after a check. #15709

New issue

Open

opened 2026-02-22 02:24:55 -05:00 by deekerman · 1 comment

deekerman commented

2026-02-22 02:24:55 -05:00

Owner

Originally created by @Zenya393 on GitHub (Apr 24, 2024).

Suggestion

Do not automatically move previously completed torrent to the incomplete folder after a check.

Use case

When cross seeding torrents, one torrent is complete, the new torrent added is be the cross seed.
If the new torrent matches, the torrent is complete, and cross seeding is successful.

However, it is possible the newly added torrent is not exactly the same, despite same name and size.
In this case, QBT should:

Do a check to see if the two files are exactly the same.
If checksums do not match, put added torrent into "error" status.
Do not attempt to start new torrent.
Do not attempt to move new torrent to "incomplete" folder. As this will also move the completed torrent too.

QBT automatically does #4 after the check. This moves the completed torrent.

Sometimes the last remaining amount is 16MB, and isn't worth moving the file.
I rather see the torrent go to error status, and allowing me the opportunity to rename the folder and/or file.

Extra info/examples/attachments

When "Automatic Torrent Management" is disabled for a torrent, that should include not automatically moving a torrent back and forth between the complete and incomplete folder.

There should be an option to disable/ignore the "Keep incomplete torrents in" option per torrent (or make part of Automatic Torrent Management).

Originally created by @Zenya393 on GitHub (Apr 24, 2024). ### Suggestion Do not automatically move previously completed torrent to the incomplete folder after a check. ### Use case When cross seeding torrents, one torrent is complete, the new torrent added is be the cross seed. If the new torrent matches, the torrent is complete, and cross seeding is successful. However, it is possible the newly added torrent is not exactly the same, despite same name and size. In this case, QBT should: 1) Do a check to see if the two files are exactly the same. 2) If checksums do not match, put added torrent into "error" status. 3) Do not attempt to start new torrent. 4) Do not attempt to move new torrent to "incomplete" folder. As this will also move the completed torrent too. QBT automatically does #4 after the check. This moves the completed torrent. Sometimes the last remaining amount is 16MB, and isn't worth moving the file. I rather see the torrent go to error status, and allowing me the opportunity to rename the folder and/or file. ### Extra info/examples/attachments When "Automatic Torrent Management" is disabled for a torrent, that should include not automatically moving a torrent back and forth between the complete and incomplete folder. There should be an option to disable/ignore the "Keep incomplete torrents in" option per torrent (or make part of Automatic Torrent Management).

deekerman added the

Feature request

label

2026-02-22 02:24:55 -05:00

deekerman commented

2026-02-22 02:25:03 -05:00

Author

Owner

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