Repository navigation
Tailoring "Torrent completed" notifications #1952
Replies: 1 comment
Agent BriefCategory: enhancement Current behavior: Desired behavior: Discussion #2063 was closed as a duplicate of this one and adds two points worth carrying: the category choices should come from the connected instance rather than free text, and the rules may need to be per event rather than one set for the whole target. Key interfaces:
Acceptance criteria:
Out of scope:
Why a human: Feature scope is a maintainer call. Whether the rules sit per target or per event, and whether tags ship alongside categories or land later, decides the schema and the settings UI. |
Uh oh!
There was an error while loading. Please reload this page.
I like being notified when a torrent I added manually finishes downloading. I care less about torrents that were added by *arr, and don't care at all about cross-seeds Qui added in the background. I'd like to include or exclude specific tags or categories when notifications are triggered.
All reactions