Actual Start/End Date not auto-populating appropriately on change request (standard, normal, and emergency)Issue Actual Start/End Date not auto-populating appropriately on any type of change request (standard, normal, and emergency) when you move it to Implement state.ReleaseAll releasesCauseIn Out-of-the Box instances, a Business rule called "State model - Can change state?" with sys_id "f3fbe0d8cb200200d71cb9c0c24c9c93" is responsible for populating the actual start/end dates. It was customized and causing an issue. The condition on the Business rule "!gs.hasRole('admin')" was removed and caused issues. Resolution- Please go to the custom Business rule, "State model - Can change state?" with sys_id "f3fbe0d8cb200200d71cb9c0c24c9c93" - Try to revert to Out-of-the Box version to observe it resolves the issue. - Then, incorporate your customization to make sure it works as per your business requirements. NOTE: Please test any changes a sub-prod instance to verify any scenarios you anticipate, before applying to a Production instance.