Currently there is an option to edit migration scripts however edits will not get applied to other environments if the old version of the script was already run.

Imagine the scenario where a migration script is created to update one record in a table that does not have it's data versioned. The script is checked in and deployed to the CI environment and the QA (test) environment. QA test finds that the update was incorrect. Development edits the migration script to correct it. The edited script will not get run again on those environments.

Currently there are only two work arounds we are aware of. Create a second migration script and leave the original incorrect one, both to be run in production. Or, manually go in to the [RedGateLocal].[DeploymentMetadata] and delete the rows that mark the script deployed.

We would like to see a checkbox or similar feature to mark an edited migration script to be run again, even though the original version had already been run on some environments.