Some tasks change unexpectedly to Zero (0) day duration (Durations zero out) when opening a project from Clarity PPM and as a result Microsoft Project (MSP) coverts the tasks into milestones. Situations where this may happen include if there are zero ETCs on the task, even if someone is assigned.
Steps to reproduce the issue when a task with one or more resource's assigned is marked completed and there are no actuals:
Expected Results: Task duration doesn't change, and the task is not a milestone
Actual Results: Task duration is changed to 0 days, and the task is then changed to a milestone
Note: If you save the project back to Clarity, the task is then also a milestone there as well. If you notice any incorrect data in MSP, it's recommended to not save the project back to Clarity as the data will be incorrect there as well.
This can happen if:
2. This is also by design in the scenario where a resource is allocated 0% on a project team in Clarity, and the resource is assigned a new task (Fixed Work or Fixed Units task type) in MSP.
3. If the task Type if Fixed Units and there is no ETCs or actual work on the task.
Release: All Supported Releases
Component: Clarity Microsoft Project Integration
Some best practices to prevent this issue:
4. For tasks without ETCs/Actuals that are still open, use a task type of Fixed Duration to prevent the tasks from being converted to Milestones.
5. Additionally, check to make sure you are on a supported Microsoft Project update (it's recommended to be on the latest version). See Microsoft Project monthly patches impact with Clarity
For a list of many known MSP issues/defects see: