starred/Radarr

Fork 0

mirror of https://github.com/Radarr/Radarr.git synced 2026-03-02 22:57:34 -05:00

Overseerr/Jellyseerr Auto Tag Funktion broken #9274

New issue

Closed

opened 2026-02-20 00:12:22 -05:00 by deekerman · 5 comments

deekerman commented

2026-02-20 00:12:22 -05:00

Owner

Originally created by @ZEROX7 on GitHub (Sep 27, 2025).

Is there an existing issue for this?

I have searched the existing open and closed issues

Current Behavior

Both services Fail to add a movie to Radarr since Radarr fails to create the tag

Expected Behavior

in Radarr v5.28.0.10205 a movie got added and the tag "6 - t3chnopsycho" got created and added

Steps To Reproduce

Eneable Auto Tag funktion inside Overseerr/Jellyseerr for Radarr Service,
Request a Movie from a NEW user ( Radarr cant have the tag already)
Overseerr wil display that it failed Jellyseerr will not
But looking at the logs both fail to add the new movie

Environment

WORKING
- OS: TrueNas Scale 25.04.2.4
- Radarr: App Version: v5.28.0.10205, Version:v1.3.18
- Docker Install: Yes
- Database: Sqlite 3.49.2
NOT WORKING
- OS: TrueNas Scale 25.04.2.4
- Radarr: App Version: v6.0.0.10217, Version: v1.3.21
- Docker Install: Yes
- Database: Sqlite 3.49.2

What branch are you running?

Master

Trace Logs? Not Optional

radarr.trace.0.txt
radarr.trace.txt

Trace Logs have been provided as applicable. Reports will be closed if the required logs are not provided.

I have read and followed the steps in the wiki link above and provided the required trace logs - the logs contain trace - that are relevant and show this issue.

Originally created by @ZEROX7 on GitHub (Sep 27, 2025). ### Is there an existing issue for this? - [x] I have searched the existing open and closed issues ### Current Behavior Both services Fail to add a movie to Radarr since Radarr fails to create the tag ### Expected Behavior in Radarr v5.28.0.10205 a movie got added and the tag "6 - t3chnopsycho" got created and added ### Steps To Reproduce Eneable Auto Tag funktion inside Overseerr/Jellyseerr for Radarr Service, Request a Movie from a NEW user ( Radarr cant have the tag already) Overseerr wil display that it failed Jellyseerr will not But looking at the logs both fail to add the new movie ### Environment ```markdown WORKING - OS: TrueNas Scale 25.04.2.4 - Radarr: App Version: v5.28.0.10205, Version:v1.3.18 - Docker Install: Yes - Database: Sqlite 3.49.2 NOT WORKING - OS: TrueNas Scale 25.04.2.4 - Radarr: App Version: v6.0.0.10217, Version: v1.3.21 - Docker Install: Yes - Database: Sqlite 3.49.2 ``` ### What branch are you running? Master ### Trace Logs? **Not Optional** [radarr.trace.0.txt](https://github.com/user-attachments/files/22575644/radarr.trace.0.txt) [radarr.trace.txt](https://github.com/user-attachments/files/22575643/radarr.trace.txt) ### Trace Logs have been provided as applicable. Reports will be closed if the required logs are not provided. - [x] I have read and followed the steps in the wiki link above and provided the required trace logs - the logs contain `trace` - that are relevant and show this issue.

deekerman

2026-02-20 00:12:22 -05:00

closed this issue
added the
Status: Confirmed

Status: Won't Fix

Area: API

Area: Notifications

Type: External Bug
labels

deekerman commented

2026-02-20 00:12:23 -05:00

Author

Owner

@bakerboy448 commented on GitHub (Sep 27, 2025):

Not a bug. Starr shouldn't have supported spaces for tags in the api. V6 fixes this and adds validation (thanks B)
JS/OS will need to 1) cease support of tags with spaces and 2)should migrate existing tags with spaces for easier UX

@bakerboy448 commented on GitHub (Sep 27, 2025): - Not a bug. Starr shouldn't have supported spaces for tags in the api. V6 fixes this and adds validation (thanks B) - JS/OS will need to 1) cease support of tags with spaces and 2)should migrate existing tags with spaces for easier UX

deekerman commented

2026-02-20 00:12:23 -05:00

Author

Owner

@bakerboy448 commented on GitHub (Sep 27, 2025):

https://github.com/fallenbagel/jellyseerr/pull/1913

@bakerboy448 commented on GitHub (Sep 27, 2025): https://github.com/fallenbagel/jellyseerr/pull/1913

deekerman commented

2026-02-20 00:12:24 -05:00

Author

Owner

@gauthier-th commented on GitHub (Sep 28, 2025):

JS/OS will need to 1) cease support of tags with spaces and 2)should migrate existing tags with spaces for easier UX

The patch I implemented in Jellyseerr is only doing 1) but is still using old tags with a space if they already exists.

Do you think we should we keep this behavior? Or force the migration to tags without space even for the existing ones, risking breaking user automations?
Or should this migration comes from *arr itself, since the server-side validation changed there?

@gauthier-th commented on GitHub (Sep 28, 2025): > JS/OS will need to 1) cease support of tags with spaces and 2)should migrate existing tags with spaces for easier UX The patch I implemented in Jellyseerr is only doing 1) but is still using old tags with a space if they already exists. Do you think we should we keep this behavior? Or force the migration to tags without space even for the existing ones, risking breaking user automations? Or should this migration comes from *arr itself, since the server-side validation changed there?

deekerman commented

2026-02-20 00:12:24 -05:00

Author

Owner

@ZEROX7 commented on GitHub (Sep 28, 2025):

shouldnt (2 be handled by radarr/sonarr? since it also needs to readd the tags since the format changed?

@ZEROX7 commented on GitHub (Sep 28, 2025): shouldnt (2 be handled by radarr/sonarr? since it also needs to readd the tags since the format changed?

deekerman commented

2026-02-20 00:12:24 -05:00

Author

Owner

@bakerboy448 commented on GitHub (Sep 28, 2025):

No plans to migrate existing tag names and probably break existing apps. Third party apps that created these tags - given the UI has never supported tags with spaces - will need to adjust their usage going forward.

It'd likely be worth migrating but to each app their own

@bakerboy448 commented on GitHub (Sep 28, 2025): No plans to migrate existing tag names and probably break existing apps. Third party apps that created these tags - given the UI has never supported tags with spaces - will need to adjust their usage going forward. It'd likely be worth migrating but to each app their own