Replies: 1 comment
-
|
Seerr is not designed to manage media. It's designed to manage requests, and send them to the *arr stack. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Seerr's issue reporting system is great for surfacing problems (bad encodes, audio sync issues, artifacts, wrong language, etc.) but the workflow dead-ends there. There's no path from "user reported a problem" to "get a better copy" without an admin manually going into Radarr or Sonarr to blocklist the file and trigger a new search.
Proposed Feature
Add a per-user permission (similar to the existing auto-approve request permission) that enables automatic issue resolution. When a user with this permission reports an issue on a media item, Seerr would:
Call the appropriate Radarr/Sonarr API to delete the current file and blocklist the release
Trigger an automatic search for a replacement
Update the issue status in Seerr to reflect that a re-download has been initiated
Why per-user permission matters
Not all users should be able to trigger re-downloads... that's a potentially disruptive action. Admins should be able to grant this to trusted users (family members, power users) while leaving regular users on the standard report-and-wait workflow.
Integration points
Radarr and Sonarr both expose API endpoints for this already.. delete file + blocklist (DELETE /api/v3/moviefile/{id} with blocklist flag in Radarr, equivalent in Sonarr), followed by a command to trigger a new search. Seerr already has service integrations with both, so the plumbing is largely there.
Beta Was this translation helpful? Give feedback.
All reactions