mirror of
https://github.com/Radarr/Radarr.git
synced 2026-03-02 22:57:34 -05:00
Ability to blocklist a release on search tab #5570
Labels
No labels
Area: API
Area: Database
Area: Db-migration
Area: Download Clients
Area: Extras
Area: Import Lists
Area: Indexer
Area: Metadata API
Area: Notifications
Area: Organizer
Area: Parser
Area: Scanning
Area: Tooling
Area: UI
Area: Unit Tests
On Hold: MetadataAPI Blocking
On Hold: MetadataAPI Blocking
Priority: High
Priority: Low
Priority: Medium
Status: Accepted
Status: Cannot Reproduce
Status: Confirmed
Status: Help Wanted
Status: In Progress
Status: Indexer - need invite
Status: Info Needed
Status: Investigating
Status: Logs Needed
Status: Maybe One Day
Status: Needs Triage
Status: On Hold
Status: Ready for Review
Status: Unlikely
Status: Waiting for OP
Status: Won't Fix
Type: Bug
Type: Documentation
Type: Duplicate
Type: Enhancement
Type: External Bug
Type: Feature Request
Type: Regression
Type: Support
Type: Support.
conflict
lidarr-pull
no-conflict
not-pulled
readarr-pull
readarr-pull
sonarr upstream
sonarr-pull
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/Radarr#5570
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @SugarDroid on GitHub (Feb 9, 2021).
Is your feature request related to a problem? Please describe.
If I want to blacklist a release then have to add it to queue, then hop to queue and blacklist it, then hop back to the movie and start over. Very inconvenient.
Since the reason of blacklisting is not related to group but the actual release only, and because of garbage naming, custom format is useless for this.
Describe the solution you'd like
Ability to blacklist release(s) without the necessity of send into queue.
Additional context

AB#697
@stale[bot] commented on GitHub (Jun 10, 2021):
This issue has been automatically marked as stale because it has not had recent activity. Please verify that this is still an issue with the latest version of Radarr and report back. Otherwise this issue will be closed.
@snorkrat commented on GitHub (Jun 3, 2024):
+1 For blocklist adding on interactive search.
@AN1MATEK commented on GitHub (Dec 31, 2024):
+1 from me
@jlj945 commented on GitHub (Jul 6, 2025):
+1 from me as well
@joachimtingvold commented on GitHub (Aug 1, 2025):
Why not make it even more flexible; add a freetext/regex-field available under each movie, where you can add blocklist-entries for that particular movie. As a recent example, a lot of false-positive "Formula1.*"-releases has been downloaded for the F1 movie. Being able to do a "^Formula1.*" regex blocklist entry for that movie in particular, would be very useful.
@bakerboy448 commented on GitHub (Aug 2, 2025):
No plans for this. You can already create filters for interactive searches.
@joachimtingvold commented on GitHub (Aug 2, 2025):
That doesn't really help with the specific problem I mentioned. Example strings that Radarr have attempted to download in the last couple of days (all of which is wrong, and has nothing to do with the actual F1 movie);
It's not really feasible to blocklist these one-by-one from the interactive search, as they are all unique, and new ones pop up every day.
This might be a different underlying problem that causes this, but would still be useful to do easy regex blocklist entries for scenarios like this.
@bakerboy448 commented on GitHub (Aug 2, 2025):
@joachimtingvold For support and inquiries, please use our Discord channel. GitHub is designated solely for bug reports and feature requests. It seems that this issue may fall under a support request, so we kindly ask you to visit our Discord for assistance. Thank you.
Radarr grabs them as your indexer incorrectly reports it as matching the F1 movie. Import would likely be blocked for AKA.
Visit Discord for support and do not add completely unrelated issues / comments.
The ask of this FR is to be able to blocklist from interactive search result. Any regex filtering thus is irrelevant as interactive searches can already be filtered.
@joachimtingvold commented on GitHub (Aug 2, 2025):
If interactive searches can be used to add blocklist entries, why is this issue still open?
As for "my" feature request, I created #11188 to cover that.