|
Moving to the next release as I won't be able to finish these today See http://musicbrainz.1054305.n4.nabble.com/Assigning-bugs-to-Fix-Versions-releases-in-Jira-tt3694435.html#none Agreed to fix within 3 months in #musicbrianz-devel and through the scheduling game. Still happened to someone http://forums.musicbrainz.org/viewtopic.php?id=4080 If I understand that forum thread correctly the behaviour described is not a bug, but intended. I don't see how this is resolved in any satisfactory way or how closing this ticket will lead to a better user experience. The behaviour is not one that the user would expect; and indeed if information is going to be /lost/ during the editing process, the user needs to either be suitably warned that an action will cause loss of information (e.g. the ToC), or prevented from doing it - depending on the least-bad course of action. I did not understand the forum thread correctly. I understood the problem to be that a DiscID attached to the tracklist of the release being duplicated didn't carry over into the newly added releases. But the DiscID is submitted as part of the request to make a new release, and that DiscID is being lost if an existing tracklist is selected. |
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Probably won't make tonight, but highlighting anyway