-
Bug
-
Resolution: Fixed
-
High
-
None
-
None
-
None
I experienced this bug 2 times now, both times when I was adding a release and re-using an already existing recording. The second time it happened by adding the following release: https://beta.musicbrainz.org/release/5f1ace23-3f4f-4eba-b00a-586d15c43a3e . During the editing when I was on the Recordings page, I selected the first recording in the list (which is https://beta.musicbrainz.org/recording/0e28d181-bf4d-4357-9eae-5cdad63d3a95), then pressed enter. After adding the release, I can see that the recording used for the track is actually not the first recording that I selected from the list, but the last recording from the list (https://beta.musicbrainz.org/recording/00454b61-5818-458a-8d0d-1969c1fc76cd). Additionally, when I go to edit release and select the correct recording and proceed with the edit, the Edit Note tab tells me that I haven't made any changes (I think the changes briefly flash for a split second there). This issue is only present on the beta site.
[MBS-9709] Beta: Re-using the existing recording will use a different one from the suggested list
| Resolution | New: Fixed [ 1 ] | |
| Status | Original: Review Submitted [ 5 ] | New: Closed [ 6 ] |
| Assignee | New: yvanzo [ yvanzo ] | |
| Status | Original: Open [ 1 ] | New: Review Submitted [ 5 ] |
I also experienced something similar i think; I was adding a release. then when selecting recordings, for one i chose an excising recording. however later after looking more thoroughly i decided it's better to create a new recording jut to be sure (this is classic music )
however after going to the final screen it shows as having attached (and not with a grey/lined text with alt: "this will be created" etc)
going back to the recordings tab shows it as attached to a recording (and not the previously chosen one, a different one)
going back and forth after re-setting as "create new recording" yielded all kinds of unpredictable results that also bleeded into the track/recording above it, eventually managed to fix it ,but it was very frustrating.
| Priority | Original: Normal [ 6 ] | New: High [ 3 ] |
I am wondering, is there a way to check how many tracks/recordings could have been affected by this bug? I don't know how many people are editing via the beta site, but if I experienced it 2 (or maybe even 3 times, because I had to fix https://musicbrainz.org/recording/bc8929b6-1eb2-4b51-bf36-b6317db15fda as well), I wonder how many times it could have happened to other people. There's also https://tickets.metabrainz.org/browse/MBS-9710 which might or might not be related to this bug...