The search results displayed by the release group autocomplete input at /release/add often don't include the release group that I'm looking for. This doesn't matter when manually adding a release via the "Add release" link on an RG page (since the RG is pre-filled), but it's painful when seeding a new release from an online source.

With Metallica in the artist field, I'd expect a search for "master of puppets" to prioritize the identically-named album release group credited to Metallica. Instead, the suggestions prioritize a bunch of RGs with the same name by unrelated (and often obscure) artists.

Part of this seems like a search ranking issue: the top result is this RG by German DJ Wollion, which seems unlikely to be what people are looking for when they search for RGs named "Master of Puppets".

But even ignoring ranking, I can see that the query used to get the suggestions only includes the autocomplete text itself, i.e. https://musicbrainz.org/ws/js/release-group?q=master+of+puppets&page=1&direct=false. When searching for a common name, there are bound to be cases where the desired RG won't be among the "best" results.

Would it be reasonable to also include the artist name in the query? When I instead search for "master of puppets metallica", the top two results are the single and album by Metallica. One consideration is that I'm not sure if it'd be better to use the artist entity's base name or the credited-as name.

Another approach could be making the autocomplete control sort the search results so that RGs matching the release artist are prioritized, but that won't help with the common-name case described above when none of the artist's RGs happen to be included in the search results.

This page looks like it's using the deprecated Autocomplete code (/root/static/scripts/common/MB/Control/Autocomplete.js) rather than Autocomplete2. Would a change to include the artist name in these RG queries still be accepted? Is there a better way to improve these results?