When updating a job usually things happen different to as planned so even milestone activities must be updated correctly.
Sometimes the actual date of a Milestone is not clear and errors do happen so I wonder if there is a way to model Milestones that do not require updating, like if a special kind of link, that will be scheduled [ASAP/ALAP] based on predecessor actual no matter how different from as planned. Essentially a way to make this activities [or special links] actual dates to be a computed value not an input value.
Maybe there is [or can be] a way to set actual dates for selected/marked activities to be computed as per actual predecessor dates before transferring to performance archive, a functionality not limited to milestones.
Perhaps I am missing something and there is an easy way to update these Milestones to automatically fit what really [ should have ] happened without creating out-of-sequence issues.