sct / overseerr

Request management and media discovery tool for the Plex ecosystem
https://overseerr.dev
MIT License
3.76k stars 437 forks source link

Handling of multiple Radarr/Sonarr instances (profiles/paths) #3615

Open AurimasNav opened 1 year ago

AurimasNav commented 1 year ago

Description

Most users are oblivious of radarr/sonarr and all the inner workings of arr stack as they only interact with plex and overseerr, so there are a lot of confusion when requesting stuff, first of all they are unaware that default request button is for non-4k instance, then they are unaware if they should choose some specific *arr instance (and the reason is that we split profiles per different arr instances to be able to have few versions of same media download), paths also mean nothing for end users.

Overseerr could streamline the experience so the user only has to pick quality profile and overseer picks the relevant sonarr/radarr instance and path.

Desired Behavior

Example scenario: radarr profiles - HD, IT, kids radarr paths - /movies, /kids

4K-radarr has profiles - 4K, FR 4k-radarr paths - /movies

For context: IT, FR profiles are configured to only download content which is in IT / FR language. HD is default language (EN) but does not allow content above 1080p. 4K is default language (EN), but does allow upgrading up to 4K. kids - prefers native language (let's say IT for example), but also allows downloads in EN, and has all qualities in a same group as it values language above quality upgrades.

With this configuration we achieve that media might be requested in IT and FR simultaneously.

Currently user would have to select if he wants to request 4k or non-4k initially, then he will see the available profiles and then there are also paths.

How I would like it to work is for user to only see profiles in selection: HD 4K kids IT FR

Overseer would have default path preconfigured for each profile in advance and therefore user should only need to make one selection when requesting.

Additional Context

I realize there are caveats when there might be quality profiles on multiple radarrs with identical names, but it could be treated as non-issue by simply selecting random one (reasoning that if you as an admin are not picky to name profiles differently you don't really care which arr instance will be used), alternatively as an admin you could choose which profile to hide if t here are name clashes, or don't allow to add another arr instance until profile name clashes are resolved.

Code of Conduct

AurimasNav commented 7 months ago

I think (hope) this will be covered by custom request routing feature mentioned in https://github.com/sct/overseerr/issues/1881

stale[bot] commented 5 months ago

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.