Elapsed durations in the MSP interface expected behavior
search cancel

Elapsed durations in the MSP interface expected behavior


Article ID: 16531


Updated On:


Clarity PPM SaaS Clarity 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)
    • See more examples at: Elapsed Durations in Microsoft Project
  • In MSP, you can define elapsed duration in days, weeks, or months only (hours are not supported).
  • When you create an elapsed duration using the above supported duration types, the elapsed duration is retained upon saving to Clarity and then re-exporting to MSP

Additional Information

Reference Elapsed Durations in Microsoft Project for more information