If I’m not mistaken, Spotify mappings must be matched manually. But some releases already have Spotify links, but they are not detected by CB to be used as mapping for release groups. When there are no conflicting Spotify links within a release group (that could be the case when two releases of the same release groups have two different entries on Spotify), why aren’t existing Spotify links used for mapping?
1 Like
Because no one’s coded it. Feel free to submit a PR to mbspotify:
1 Like
Is there already a ticket for this in JIRA? At least there should be one, so that if @silentbird can’t or doesn’t have the time to write that someone else will maybe see it and look into it 
3 Likes
Issue created: https://tickets.metabrainz.org/browse/CB-350. I can’t do anything with development, so thank you to whomever will be assigned to the ticket.