You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Thank you for the latest 2.x updates, having the delete media button for lower privileged users is fantastic! However, I believe the delete media feature is missing one very important functionality: Blocklist the release in Sonarr/Radarr. Oftentimes when media is deleted, I don't want to really delete it, I just want Sonarr/Radarr to delete and download another release. For example if a file was incorrectly indexed and in the wrong language, I want to replace the file with another.
And for this, the delete media feature could really shine: If the user either has another button "Delete & Blocklist" or gets asked after pressing the "Delete Media" button if it should be blocklisted too. Once the file is deleted and blocklisted, Sonarr/Radarr can search for a new file again and doesn't download the previous file again.
Desired Behavior
Ideally, there are two buttons:
Remove from Sonarr/Radarr
Remove & Blocklist from Sonarr/Radarr
If the first button is pressed, the file gets deleted identically to now. If the second button is pressed, it will delete the file as with the first button but also add this particular release to the blocklist by marking it as failed. This behaviour would be identical to when one deletes the file via the history tab in the specific media page in Sonarr/Radarr. After pressing the delete button, one can "Mark as Failed", which will blocklist the release and search for a new release.
Additional Context
I believe this feature would be different to issues like #1039 and sct/overseerr#3941 as those issues focus on the List Exclusion being synced with the Jellyseerr blacklist. My feature request focuses on basically downloading a new release because the initially downloaded one isn't wanted.
Thank you so much for investing so much time and efforts in providing us with Jellyseerr! I absolute love it!
Code of Conduct
I agree to follow Jellyseerr's Code of Conduct
The text was updated successfully, but these errors were encountered:
Description
Thank you for the latest 2.x updates, having the delete media button for lower privileged users is fantastic! However, I believe the delete media feature is missing one very important functionality: Blocklist the release in Sonarr/Radarr. Oftentimes when media is deleted, I don't want to really delete it, I just want Sonarr/Radarr to delete and download another release. For example if a file was incorrectly indexed and in the wrong language, I want to replace the file with another.
And for this, the delete media feature could really shine: If the user either has another button "Delete & Blocklist" or gets asked after pressing the "Delete Media" button if it should be blocklisted too. Once the file is deleted and blocklisted, Sonarr/Radarr can search for a new file again and doesn't download the previous file again.
Desired Behavior
Ideally, there are two buttons:
If the first button is pressed, the file gets deleted identically to now. If the second button is pressed, it will delete the file as with the first button but also add this particular release to the blocklist by marking it as failed. This behaviour would be identical to when one deletes the file via the history tab in the specific media page in Sonarr/Radarr. After pressing the delete button, one can "Mark as Failed", which will blocklist the release and search for a new release.
Additional Context
I believe this feature would be different to issues like #1039 and sct/overseerr#3941 as those issues focus on the List Exclusion being synced with the Jellyseerr blacklist. My feature request focuses on basically downloading a new release because the initially downloaded one isn't wanted.
Thank you so much for investing so much time and efforts in providing us with Jellyseerr! I absolute love it!
Code of Conduct
The text was updated successfully, but these errors were encountered: