none
PS2010 - Assignment Delay set automatically RRS feed

  • Question

  • I have following annoying issue with Project Server 2010. Every now and then, the system enters automatically an assignment delay of >100 days, which causes moving all successors forward in time…

    What I know about the problem is that:

    1. The Project Owner certainly did not add the assignment delay manually in the plan
    2. The resources in question have not submitted actuals on the task in question
    3. When you manually put the assignment delay back to 0, the delay automatically comes back when saving the plan
    4. When you manually enter Work in the Task Usage view between the task Start Date, and the task Start Date + Assignment Delay date the systems enters automatically Actual Work as well (so if you give in 5h of work on a certain day, MSP enters 5h of work AND 5h Actual Work) and then complains about entering Actuals manually while the server flag “Only allow task updates via Tasks and Timesheets” is checked…
    Any help?

     



    Tuesday, January 22, 2013 5:40 PM

Answers

  • Mayor, have your investigations so far come up with any patterns? Is the effect limited to any particuar projects or resources? What does the Task Inspector show? Is it just the assignment that is affected or the task?

    One cause that is not always easy to spot is task dependencies involving summary tasks. If the affected task is under a summary task which has a predecessor - and that predecessor is delayed beyond the start of the summary task, any unstarted tasks under the summary will be delayed according to the dependencyeven though you do not see the dependency listed for the affected task!

    Graham

    • Marked as answer by THREON - BVO Friday, January 25, 2013 10:55 AM
    Wednesday, January 23, 2013 4:14 PM

All replies

  • Mayor, have your investigations so far come up with any patterns? Is the effect limited to any particuar projects or resources? What does the Task Inspector show? Is it just the assignment that is affected or the task?

    One cause that is not always easy to spot is task dependencies involving summary tasks. If the affected task is under a summary task which has a predecessor - and that predecessor is delayed beyond the start of the summary task, any unstarted tasks under the summary will be delayed according to the dependencyeven though you do not see the dependency listed for the affected task!

    Graham

    • Marked as answer by THREON - BVO Friday, January 25, 2013 10:55 AM
    Wednesday, January 23, 2013 4:14 PM
  • The strange behavior was indeed caused by dependencies on one of the summary tasks of the affected task...

    Thanks GMcH!!


    EPM Consultant - www.threon.com

    Friday, January 25, 2013 10:55 AM