MSP New Driver: Manually scheduled completed Milestones change to Project Start date when exported from PPM

Products

• CLARITY PPM FOR ITG
• CLARITY PPM FEDERAL
• Clarity PPM SaaS - Application
• Clarity PPM On Premise

Issue/Introduction

In the Clarity PPM Microsoft Project (MSP) New Driver, manually scheduled Milestones change to the Project Start date if the milestone is 100 % Complete. This issue doesn't happen for manually completed tasks that are not milestones or milestones that are not completed.

Prerequisite: Have the following MSP Update installed: KB4462134 (this also happens on other MSP Updates, but not in earlier updates such as the June MSP Update)

Steps to reproduce:

1. Create a project in Clarity PPM with a start date of 2/11/19
2. Export the project to MSP
3. Create one task with a start date as the project date (2/11/19)
4. Create one manually scheduled task set as a milestone with a start/finish date of 2/22/19.
5. Mark the milestone task created in step 4 as 100% complete
6. Save the project back to PPM
7. Export the project back to MSP

Expected Results: The milestone start/finish date is still 2/22/19
Actual Results: the milestone start/finish date changes to the project start date (2/11/19)

Cause

This issue is caused by DE48354. It currently appears to happen on some, but not all MSP Updates.

Environment

Release: CODFSS99000-15.5-PPM SAAS FedRAMP-Sandbox-Small Environment
Component:

Resolution

This issue is targeted to be fixed in Clarity PPM 15.6.1.

Workarounds:

Option 1: Set milestones to Task Mode of Auto Scheduled in MSP.
For already impacted milestones: Change the task to auto scheduled in MSP, then update the start/finish dates to the correct date. 

To change the Task Mode for a task:

• Option 1: Go to a task view in MSP, and select Auto Scheduled from the drop down. Any Tasks that are Manually Scheduled will have a thumb tack in the Task Mode field. 
• Option 2: Double click on the task in MSP and change Schedule Mode from Manually Scheduled to Auto Scheduled and click OK

Option 2: Revert back to an older Microsoft Project Update. Link to one MSP2016 update where it does not happen is the June 6.2017 update from Microsoft: KB3191934
Note: It's recommended to test the impact in non production to make sure reverting back doesn't introduce any issues fixed on later updates.

Additional Information

Reference KB000047129 - In the MSP New Driver, task Start Dates change to the Project Start Date when exported to MSP
Reference KB000071385 - CA PPM and MSP integration - List of Knowledge Documents
Reference KB000015956 - CA PPM and MSP integration known defects - Support Technical Document Index