We have a critical issue about "planned date" milestone:
- When the milestone is "fixed" and validated or delivered:
The "planned date" shall be the same date than the "real date" when "done" is checked.
Now, the "planned date" corresponds to the "validated date" when the milestone is fixed.
- When the milestone is "floating" and validated or delivered :
The "planned date" shall be the same date than the "real date" when "done" is checked. During planification of the projet, even if the milestone is done, the planned date is updated and does not corespond to the real date. See an example attached.
To summarize, for all milestones, if "done" is checked ==>planned date" = "real date".
Planned date (for milstones and for activities) is always result of latest planning calculation.
And when real is set, value is not planned any more.
This explains why planned date is always "last planned" date and is not equal to real.
Tnanks for your answer. I will check on the project where the issue has been tracked.
Hello,
I've checked with the Project Manager and we always have this issue. You can find attached this problem.
In this example the real is set. (28/02/2017). The value is unfornutaly planned (01/03/2017).
It is a problem for the 45° curve too. Because, it is not the real date which is displayed but the false planned date. It is a big issue about reporting for ou client.
Also, concerning the 45° curve, when the real date is set before the planned date, the 45° cuve should be displayed the real date and not the planned date.
thanks you for your anwer,
Regards
28/02/2017 is the real 'done' date as you marked it done on this date
You should change the 'done' date to fix real end date 😉
Ok to fix another real "done" date.
The issue is : "planned" date....
Hi,
It is a problem for the 45° curve too. Because, it is not the real date which is displayed but the false planned date. It is a big issue about reporting for ou client.
I understand the mismatch.
In fact planned date is always last planned date when real is set. It has been set this way to keep in mind last planned date.
But now that baselines exist, this information may no longer be pertinent. So we'll have to think about 2 solutions :
- change 45° curve to take into account this situation
- change planned date calculation behavior so that it is set to real date when this last one is set. This solution seems better but cannot be included in a patch as it brings a major evolution in calculation, so could only be deployed in V6.2.
Also, concerning the 45° curve, when the real date is set before the planned date, the 45° cuve should be displayed the real date and not the planned date.
OK, we'll have a look.
Ticket #2590 recorded
It is a problem for the 45° curve too. Because, it is not the real date which is displayed but the false planned date. It is a big issue about reporting for ou client.
Hello,
I understand the mismatch.
In fact planned date is always last planned date when real is set. It has been set this way to keep in mind last planned date.
But now that baselines exist, this information may no longer be pertinent. So we'll have to think about 2 solutions :
- change 45° curve to take into account this situation
- change planned date calculation behavior so that it is set to real date when this last one is set. This solution seems better but cannot be included in a patch as it brings a major evolution in calculation, so could only be deployed in V6.2.
When do you planned to deliver the V6.2 ?
Also, concerning the 45° curve, when the real date is set before the planned date, the 45° cuve should be displayed the real date and not the planned date.
OK, we'll have a look.
This curves are shown to our customers. It is urgent to solve this issue ASAP.
Ticket #2590 recorded
V6.2 is planned on April 17th.
We'll try and solve ticket #2590 with workaround on 45° chart on patch 6.1.2
Thanks you very much to consider our request,
Regards,
Pascal