Tracker URL as folder name in automatic downloads #8487

Closed
opened 2026-02-21 19:38:39 -05:00 by deekerman · 2 comments
Owner

Originally created by @SenatorIvy on GitHub (Mar 25, 2019).

Please provide the following information

qBittorrent version and Operating System

qb 4.1.5, Windows 10 Pro

What is the problem

Download location should be able to be set by tracker

What is the expected behavior

A folder should be created automatically in the root of downloads for each different tracker

For automatic downloads it would be nice if we could have qb automatically create folders on a per-tracker basis, so that when I download from tracker A and from tracker B, the resultant files would automatically end up in:
Downloads\Tracker A
Downloads\Tracker B
without me having to change any dropdowns or any categories.

Originally created by @SenatorIvy on GitHub (Mar 25, 2019). **Please provide the following information** ### qBittorrent version and Operating System qb 4.1.5, Windows 10 Pro ### What is the problem Download location should be able to be set by tracker ### What is the expected behavior A folder should be created automatically in the root of downloads for each different tracker For automatic downloads it would be nice if we could have qb automatically create folders on a per-tracker basis, so that when I download from tracker A and from tracker B, the resultant files would automatically end up in: Downloads\Tracker A Downloads\Tracker B without me having to change any dropdowns or any categories.
deekerman 2026-02-21 19:38:39 -05:00
Author
Owner

@thalieht commented on GitHub (Mar 25, 2019):

When #9939 is implemented then maybe.

@thalieht commented on GitHub (Mar 25, 2019): When #9939 is implemented then maybe.
Author
Owner

@sledgehammer999 commented on GitHub (Oct 29, 2020):

This issue has been closed and locked for being too old, and thus either most likely resolved in recent versions or no longer applicable.
If you experience the reported problem or similar in the latest version, please open a new issue report with the requested information in the issue template.

A new issue report with relevant updated data gathered from the latest version is preferable to necroing an old report with a comment like "still happens in version x.y.z", even if you think the bug is the same, or suspect of a regression.
Due to the changes made to the qBittorrent code and its dependencies over time, the exact cause of your problem could be totally different than the original one, despite the visible symptoms of the bug being similar.
Thus, providing relevant updated information is crucial to find and fix the root cause of a recurrent problem or regression.

Thank you for your contributions.

@sledgehammer999 commented on GitHub (Oct 29, 2020): This issue has been closed and locked for being too old, and thus either most likely resolved in recent versions or no longer applicable. If you experience the reported problem or similar in the **latest** version, please open a new issue report with the requested information in the issue template. A new issue report with relevant updated data gathered from the latest version is preferable to necroing an old report with a comment like "still happens in version x.y.z", even if you think the bug is the same, or suspect of a regression. Due to the changes made to the qBittorrent code and its dependencies over time, the exact cause of your problem could be totally different than the original one, despite the visible symptoms of the bug being similar. Thus, providing relevant updated information is crucial to find and fix the root cause of a recurrent problem or regression. Thank you for your contributions.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/qBittorrent#8487
No description provided.