25 พฤษภาคม 2553 17:03ผู้ดูแล
Found an interesting issue today, which I was curious as to why it's happening. Wondering if anyone could provide some insight. Note the issue can be reproduced in 2007 SP1, SP2, and 2010 RTM:
1) Create a task with a duration of 20+ days.
2) Set the Status Date to a nonworking day (i.e. weekend) in the middle of the task. Copy the Status Date from the Status Date Dialog Box. (Note that this step isn't stricly required, as the result can be replicated by repeatedly typing a nonworking date into the Stop field for the task.)
3) Paste the Status Date into the Stop field for the task. The task will appear to update as scheduled, which is fine.
4) Paste the Status Date into the Stop field again. The task duration will double. Paste again, and the task duration will double again. Repeat as needed.
As far as I can tell, the issue happens when the same nonworking time is repeatedly entered in the Stop field.
FYI that this is in the context of troubleshooting a macro that is rescheduling unstarted tasks/updating tasks as scheduled based on specific logic. We have a couple of workarounds that will probably work, but I thought this was an interesting challenge to throw out to the crowd for a sanity check.
25 พฤษภาคม 2553 18:47ผู้ดูแล
Just to add to the discussion:
After doing the above procedure a couple of times, the CompleteThrough field seems to revert to the Task Start, thereby removing the default Progress line from the Gantt Chart for affected tasks. The only way I could determine to recover the Progress line was to add a graphical element such as a triangle to the schedule for the CompleteThrough field, drag the triangle to the middle of the task, and then run the Update as Scheduled routine on the task to get the CompleteThrough field working again.
Following that, it seems to work ok.