Hey everyone,
I have a setup since few years now where two separate Jellyseerr instances both point to the same Sonarr server, and I'm experiencing a tag collision issue that seems like a bug.
Setup:
- My Jellyseerr : Sonarr configured as the default instance, "Add requester tag" enabled
- My friend's Jellyseerr (v3.1.0) : the same Sonarr configured as a non-default/SSL-only instance, with his own separate Sonarr as his default.
The issue:
All my Sonarr series tags got silently overwritten by my friend's instance users. The "Add requester tag" option on his side should not apply to my Sonarr since it's not his default instance. Yet it look like a job from his Seerr appeared to be renaming my global Sonarr tags anyway.
The replacement tag happened with internal user IDs start from 1 on both instances independently. So if my user ID 1 is toto and his user ID 1 is bob, it renames my global Sonarr tag 1-toto to 1-bob.
Every single series that had that user tag is affected, even for series that none of his users ever requested....
Is this a known bug in v3.1.0 where the sonarr-scan job applies requester tags even on non-default Sonarr instances ?
How can I properly re-apply all the correct Seerr users tags to my existing Sonarr library ?
Thanks in advance for your help.