ALERT: Some images may not load properly within the Knowledge Base Article. If you see a broken image, please right-click and select 'Open image in a new tab'. We apologize for this inconvenience.
Elapsed durations in the MSP interface expected behavior
Article ID: 16531
Clarity PPM SaaSClarity PPM On Premise
Elapsed durations are now supported in the Microsoft Project (MSP New Driver). What is the general behavior expected for these types of durations?
Release: All Supported
In the MSP New Driver, you are now able to use elapsed durations, here are a few key points regarding the behavior:
There is no indicator in Clarity to indicate a task duration is elapsed.
When an eduration is added to a task in MSP, when you save the project back to Clarity, the dates will reflect the elapsed duration in Clarity., but the duration will not have an indicator to show that it is elapsed.
If you modify the task start, finish, duration, or dependencies in Clarity, the durations are converted to working days. Some examples as per the documentation that can impact task dates changing in Clarity include:
Running Autoschedule against the project (via the Autoschedule job or the Clarity Gantt)
Posting actuals for task assignments
Changing the project start or finish dates (if the task's dates are outside the new dates)