#1
|
|||
|
|||
% completion changes finish date?
Hi again, found a new amazing feature in Project that I don't get I have set up a project plan and all plan dates incl. dependencies look fine. Now as soon as I enter any value in the % completion field of the first task, the plan finish date changes to a later date. Why? For the following tasks, no such issue occurs. It's just that single task. Also, this will happen on any value, i.e. even if I set 90% with which we'd be ahead of plan, it'll change. |
#2
|
|||
|
|||
Is the first task the predecessor to any other task? Is the project calculation set to "on"? Change another task (without changing the problem task) and press F9 - does anything else change?
Can you zip and attach the plan to your next post? |
#3
|
|||
|
|||
No predecessors and calculation is on.
While anonymizing the plan I played around a bit more and found that when I change scheduling to "From project start date" instead of "From project end date" the issue disappears. Nevertheless, I would like to understand this as it didn't happen with the mpps I created before and they were scheduled the same. Maybe it's an accumulated issue as the plan is based on a template? Appreciate if you could have a look |
#4
|
|||
|
|||
I have the file - which task is causing the issue?
|
#5
|
|||
|
|||
The task in line 2 ("1") is the one in question
|
#6
|
|||
|
|||
You have your project scheduled from a fixed finish date. So all of your summary tasks constraints are As Late as Possible. When added progress, I immediately got a warning from the Planning Wizard about constraints.
|
#7
|
|||
|
|||
Right, as I said, if I change to a fixed start date it disappears. Still, that behaviour didn't occur before and previous plans were scheduled the same way.
I also don't get, why this only happens for that specific task. It doesn't occur anywhere else in the chart. One of MS Project's big miracles I'll have to live with? (I can live with just changing it to 100% when done, but still I like working with percentages) |
#8
|
|||
|
|||
When I open the file and press F9, I get immediate error messages about task 97.
I can reproduce your exact issue when mixing ALAP summary tasks with ASAP subtasks. The tasks split and the remainder of the task aligns with the ALAP constraints. |
#9
|
|||
|
|||
Ok, I think I need to reconsider the complete scheduling as this keeps causing the weirdest issues.
Thanks for your help |
#10
|
|||
|
|||
I think I know why you are scheduling from a finish date - but consider switching to a start date and setting a deadline or constraint to the finish date. The mix of summary tasks with ALAP and subtasks with ASAP is, I believe, causing the unexpected results.
|
|
Similar Threads | ||||
Thread | Thread Starter | Forum | Replies | Last Post |
what to put in to schedule for dealing with overall finish date | ketanco | Project | 7 | 10-30-2014 02:25 PM |
flag to indicate finish date does not equal baseline finish date | TCB | Project | 3 | 08-06-2014 02:49 PM |
Assigning finish date to work with %complete | Guloluseus | Project | 3 | 12-12-2013 10:16 AM |
how to calculate backwards from a set finish date | ketanco | Project | 1 | 02-07-2013 06:50 AM |
remaining duration vs finish date | ketanco | Project | 3 | 02-17-2012 02:24 PM |