MSP allows non-zero day duration and Open for TE milestones

Products

• Clarity PPM On Premise
• Clarity PPM SaaS

Issue/Introduction

Clarity does not allow a Milestone to be Open for Time Entry ("Error: A Milestone Task cannot be Open for Time Entry.") and Clarity assigns a 0 day duration to Milestones that cannot be changed (the value becomes read-only).
However, if these are created or edited from Microsoft Project, it is possible to have a Milestone with a duration different than 0 and/or Open for Time Entry (and these cannot be reversed from Clarity).

Steps to Reproduce:

Observations:

• Create a miletone in Clarity
  -> Milestone has 0d duration and it is NOT Open for Time Entry. (expected)
• Create a 1d regular (non-milestone) task in Clarity
  -> Task has 1d duration and Open for Time Entry. (expected)
• Try to make the task to a Milestone
  -> "Error: A Milestone Task cannot be Open for Time Entry.". (expected)
• Close it for Time Entry, make it a Milestone
  -> Duration will change from 1d to 0d. (expected)
• Make it a non-Milestone
  -> Duration will change from 0d to 1d. (expected)

When using Clarity<->MSP:

1. Create a 1 day regular task in Clarity (1d, Open for Time Entry)
2. Open the project in MSP.
3. Make it a Milestone in MSP. Do not change anything else.
4. Save back to Clarity.

Expected Results: Milestone has 0d duration and it is not Open for Time Entry. There is no way to change these values from Clarity UI. Duration can be changed from MSP, but for adjusting Open for Time Entry flag in MSP, it is necessary to create a new MSP Field Mapping to close the task for Time Entry.

Actual Results: Milestone has 1d duration and it is Open for Time Entry.

Environment

Release : 16.1.2

Cause

DE70674

Resolution

This issue has been fixed in Clarity 16.2.0.