Sonarr version (exact version): 220.127.116.118
Mono version (if Sonarr is not running on Windows): 18.104.22.168
OS: Synology DSM 6.2 - Docker - lsiodev/sonarr-preview
trace logs: https://pastebin.com/Ccs2RrJS (look for S05E08 - theres a transmission update in the middle just skip it)
1st presumption is that when you group qualities their order within the group is immaterial - from this previous thread Qualities and preferred tags weight
2nd presumption is that when you do a manual search the results are ordered in the same way that sonarr would order them to download. eg the one at the top is the one sonarr would pick if you did an automatic search (and it got the same results as the manual search)
one or both could be bad presumptions as its not currently working that way
i have a release profile with x265 h265 hevc x.265 h.265 all as +20 each and has the rename ticked (just in case that issue isnt fixed yet)
i’ve got every 720p quality variant grouped together in the quality profile (i dont care about sub quality, plus it makes things easier for later)
when i do a manual search the files are sorted in the same order as i have grouped them within the quality profile, which i didnt think they were meant to do.
the files with the preferred words are tagged correctly but as those files are 4th in the group they are on the next page, not at the top of the 720p files (due to having +20)
my presumption was that it shouldnt matter how you order the qualities within a group they all have the same order level when it comes to selecting a file, sonarr should lump all 720p files together (as they are grouped), then add the preferred words value
if i edit the quality profile and move the 4th quality to be the 1st in the group then the manual search shows them at the top and the auto search will select a file from that quality which sort of makes groups pointless
so i guess the whole preferred words with a quality really means that, they only work within the same quality, even if you group them? which makes them rather ineffective as well so i presume its a bug, maybe two?
its easily repeatable but i’ll try and upload screenshots and the trace logs i got from it!