Skip to content

Tag Selection During Request Approval/Denial #3025

@Duhato

Description

@Duhato

Description

Feature Request: Tag Selection During Request Approval/Denial

Summary:
Add the ability to assign tags to movie requests directly from the approval/denial workflow in Jellyseerr, so that Radarr can route downloads to the correct root folder without requiring a separate manual step in Radarr.

Problem:
When managing multiple root folders in Radarr (e.g. a Family Movies folder and a general Movies folder), routing is controlled by tags. Currently, when approving a request in Jellyseerr, there is no way to assign a tag at the time of approval. The admin must approve the request in Jellyseerr, then go into Radarr separately to add the correct tag before the download begins. This is a disjointed workflow that requires switching between two applications for every request.

Proposed Solution:
When an admin is approving or denying a movie request, add an optional tag selector dropdown that allows them to assign one or more Radarr tags to the request at the time of approval. The available tags would be pulled from the connected Radarr instance dynamically.

Use Case:
A user has two root folders in Radarr — one for family-friendly content and one for general movies. When a request comes in, the admin wants to approve it and simultaneously tag it as "family" so Radarr automatically routes it to the correct folder — all without leaving Jellyseerr.

Current Behavior:
No tag selection exists during the approval workflow. Tags must be manually assigned in Radarr after approval, requiring the admin to switch applications for every request.

Desired Behavior

Expected Behavior:
During request approval, an optional tag field appears allowing the admin to select from existing Radarr tags. The selected tag is passed to Radarr along with the approval, routing the download to the correct root folder automatically.

Additional Context

No response

Search Existing Issues

  • Yes, I have searched existing issues.

Code of Conduct

  • I agree to follow Seerr's Code of Conduct

Metadata

Metadata

Assignees

No one assigned

    Labels

    awaiting triageThis issue needs to be reviewed
    No fields configured for Feature.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions