Hello,
I see it as a bug, but let me know if I am wrong : the planned date of a deliverable is only updated when associated with a milestone, not when the planning changes the date of the milestone. As a consequence, the planned date of the deliverables are very complicated to use (they are wrong most of the time).
Actually, from my experience, the expected behavior would be :
- if the milestone is a fixed one : the milestone forces the 'due date' of the deliverable, the planned date is what the project manager actually expects to happen.
- if the milestone is a floating one : the deliverable is a predecessor of the milestone, in this case the due date of the deliverable is the validated date of the milestone.
my 2 cents![:)]( ":)")
I see it as a bug, but let me know if I am wrong : the planned date of a deliverable is only updated when associated with a milestone, not when the planning changes the date of the milestone. As a consequence, the planned date of the deliverables are very complicated to use (they are wrong most of the time).
Actually, from my experience, the expected behavior would be :
- if the milestone is a fixed one : the milestone forces the 'due date' of the deliverable, the planned date is what the project manager actually expects to happen.
- if the milestone is a floating one : the deliverable is a predecessor of the milestone, in this case the due date of the deliverable is the validated date of the milestone.
my 2 cents
