Loading...
Quick Links

Zombie tasks from ophaned ID

Home Forums Discussion Zombie tasks from ophaned ID

Viewing 2 posts - 1 through 2 (of 2 total)
  • Author
    Posts
  • #2182 Reply
    CommunityCommunity
    Keymaster

    This is an infrequent occurrence, but not unique. You’ve published your project plan and the team is working away and recording actual hours via PWA. Development has already started when a scope change occurs and you need to add a new analysis task. Conversely, a task like unit testing may have already started when a feature is descoped and you remove a development task. In either case, the last task with actual hours recorded suffers a task ID change. In spite of republishing your project plan, you now have the actual task ID in the project as N, but the corresponding task in PWA shows N-m or N+m. That task is now “orphaned” in PWA as Project Server merrily continues with the updated numbering. This happens in both 2003 and 2007. Has anyone determined a means of preventing or fixing this?

    #10386 Reply
    CommunityCommunity
    Keymaster

    This answer was posted elsewhere a few days after leaving my question here, so I’ll share it for the benefit of others plagued by this problem. ———————————- In Project Server 2010, when a Timesheet is created, it links each timesheet line to a Project Plan Task using the Task’s UID. If you move that Task’s location in the Project Plan by dragging it, you’ll be OK. If you “move” that Task using Cut and Paste, you’ll delete the old Task and create a new Task, with a new UID, breaking the link to the Timesheet! As long as no Actual Work has been done, that’s not an issue; once Actual Work has been logged, you can be in trouble. To be safe,avoid using Cut and Paste with Tasks in Project Professional.

Viewing 2 posts - 1 through 2 (of 2 total)
Reply To: Zombie tasks from ophaned ID
Your information: