I believe Stat Admin should have ability to change the migration status through front end through migration console when migration failed and the objects were actually successfully migrated to the target environment.
It would save on the support/maintenance overhead if environment access could be managed at the User Class level, as well as the individual user level. For example, our standard developers can migrate to Dev, Support, and SIT. This is true for all developers...
Company might have 50-100-500 Developers, DBA are 1-10. Most CSR are created at starting point with Developers.
As with current STAT, New CSR Creation, Queue is auto populated as per Alphabetically , as DBA comes before Developers.
Most developers...