Where a second edit is made to a field where there is already a pending edit, which if the first edit applies when it closes will cause the second edit to fail on "The tracklist has changed since this edit was created", there should be a warning that this might occur when the second edit is submitted.

e.g.
------------------------------------------------------------------------

There is a track on some release titled "Rapperrs Delite".

An edit is made to correct 'Delite' to 'Delight' by changing the track name to "Rapperrs Delight".

Sometime before the first edit closes, someone else has noticed "Rapperrs" is spelled wrong, hence an edit to change the track name to "Rappers Delite" is made. No warning is made at this stage that should the open (first) edit be applied in the meantime, this edit will fail.

First edit then closes and applies. Second edit is doomed to fail from this point (although again, at this point nothing happens, no warnings, and the second edit is still quite happily sitting in the voting queue)

It won't be until 14 days time (assuming there wasn't enough +ve votes in the meantime), that the second edit will fail because of the first change, greatly frustrating the user who made the edit.

------------------------------------------------------------------------

Ideally, at the time that the second edit was made, the system should have flagged up that there was an open edit affecting this field, warning that if this existing edit was to be applied, the edit the user is trying to make would fail, and perhaps encouraging them to vote on the existing edit and wait a few days for it to close. A tick box "I understand and still wish to make this edit" option should be available (to be used if for example the first edit is wrong and on it's way to being voted down).

This is sort-of related to the frustrations in MBS-2812, in the sense of the lengthy amount of time between unwittingly making a 'good' edit that is 'destined-to-fail' and the edit actually failing.