Uploaded image for project: 'MusicBrainz Server'
  1. MusicBrainz Server
  2. MBS-7442

User asked to confirm unchanged "strange" barcode

    XMLWordPrintable

    Details

      Description

      When editing a release that has a non-standard barcode, the user is asked to re-confirm it's correct as per the release (see http://beta.musicbrainz.org/release/88711a95-6c2a-4b46-b3a5-f94d60765804/edit for an example).

      This seems just wrong - there's no reason we should be asking a user who didn't actually enter nor modify the barcode to confirm it's correct. There's no particular reason they need to even be able to do so - a user might want to fix capitalisation for a release they don't have, yet be forced to lie and say they're sure the barcode is like that on the release.

        Attachments

          Activity

            People

            Assignee:
            bitmap Michael Wiencek
            Reporter:
            reosarevok Nicolás Tamargo
            Votes:
            2 Vote for this issue
            Watchers:
            0 Start watching this issue

              Dates

              Due:
              Created:
              Updated:
              Resolved:

                Packages

                Version Package
                2015-02-09