Under Review
over 6 years ago

Ability to build and save a release for future use

Mass Migration by Release is an attractive looking feature but, in our experience, not really practical.  I would be useful to be able to change the migration order of CSRs, Archive Sets, and Objects at the release level (which I'm sure was in 5.6 but no longer in 5.8) and then save that, so the release could be built ahead of the actual migration.