Zero hours on zero tasks forwarded on archived projects

[kevin.platea]

I have archived several projects, per the standard archive process:
set booking to proposed, tasks @ 100%, then archive in PWA.

however, when a resource submits status updates (time entry) on other
projects - the archived projects are submitting time (at zero hours) to
project managers for approval

Any chance there is a way of not making that happen - programmatically?

(e-mail address removed)

 

[Gary L. Chefetz [MVP]]

Kevin:

If you set the booking type for all resources to proposed, and updates are
still going out, then you likely have some orphaned assignments in the
system. Look at the affected users timesheets to figure out what's going on.
Things like tasks that were deleted by the PM but not hidden from the
timesheet, tasks that were incorrectly deleted or rejected new tasks can all
cause this behavior. You can have the users hide these or you can run a SQL
query to hide them.