The undo feature automatically disables your database triggers. I don't want my database triggers disabled.
We use DB triggers to track schema changes. If we use the Undo feature, it disables the triggers and we no longer are able to record the history apart from our source control system. Source Control is great, but we need to know exactly who made changes and when.
AdminJames Billings (Admin, Redgate) commented
Normally, if our engine has to disable triggers during an update, it should re-enable them afterwards again. The Undo option will basically update your DB to the copy from the repository- if the object you're updating has a trigger on it in the repo, that should survive intact after the undo process. If, we're disabling triggers on related objects to the one you're undo-ing, and not re-enabling them afterwards, that sounds more like a bug, and a specific example would be useful.