none
Tasks were deleted/moved by Project Managers after Time was reported by contributors RRS feed

  • Question

  • So here is the most bafling situation I have at hands. We are running MS Project Server 2010. There are many projects where users are assigned and time is being reported. Few of the PMs managed to moved the tasks where time was already reported to other projects. Now I have timesheets that have UID that no longer exists.

    The actual steps of events might have gone in the following way:

    1. Project was setup with Tasks and users were assigned

    2. Project was then checked in and published

    3. Time was reported by the users and somewhere PM checked out the project

    4. PM never checks the project back in and the moves the tasks around

    5. PM then check-in and publish and -- voila  -- tasks with timesheet disappears

    If this is a client server technology then it should not have happened but it did.

    Questions

    - Has anyone else encountered a similar situation and how they went about fixing it besides the user training?

    - How to fix the ongoing issue?

    Many thanks for your help.

    Wednesday, January 29, 2014 6:41 PM

Answers

  • Hi,

    to stop this happening in future, try to think about point 3.

    The issue is, as long as Actuals are only entered and saved, but not submitted, PM does not get an information when opening his project. And if not yet approved, he will not get a wrning when deleting a task. So as you wrote initialy "how they went about fixing it besides the user training" ... Try to train your resources to submit their updates regularily - not timesheet, but just selected tasks after entering hours. And train your PMs to checking  Approval Center before making changes like this. If processes like submitting and approving are not used, system can't stop this kind of actions. At least not that I am aware of.

    Sorry!
    Barbara

    _______________________________________________________________________________
    To increase the value of this forum, please mark the replies that helped to solve your issue as answer. If you find answers to questions from other forum participants to be helpful, please mark them as helpful. Your participation will help others to find an appropriate solution faster.
    Thanks for your support!

    Wednesday, February 5, 2014 10:20 PM
    Moderator

All replies

  • Hi,

    a few questions up front:

    Do you use Single Entry Mode (SEM). What page are your users using: really timesheets or are they entering time on tasks page. Are users submitting their actuals or just saving? When the submit and PM is also Status Manager of these tasks, he gets an information that updates are pending when opening project plan. If he deletes tasks with actual work, he is also informed that it was no good idea.

    To avoid this situation, I suggest to

    Let us know, how you are working right now and if my suggestions may be an option.

    Barbara


    _________________________________________________________________________
    To increase the value of this forum, please mark the replies that helped to solve your issue as answer. If you find answers to questions from other forum participants to be helpful, please mark them as helpful. Your participation will help others to find an appropriate solution faster.
    Thanks for your support!
    Wednesday, February 5, 2014 7:09 PM
    Moderator
  • Thanks so much for the reply.

    Time is entered only through the timesheets page - SEM. We do not allow to enter time through Tasks update. That is the reason we are puzzled how did that happen.

    Wednesday, February 5, 2014 9:31 PM
  • Hi,

    to stop this happening in future, try to think about point 3.

    The issue is, as long as Actuals are only entered and saved, but not submitted, PM does not get an information when opening his project. And if not yet approved, he will not get a wrning when deleting a task. So as you wrote initialy "how they went about fixing it besides the user training" ... Try to train your resources to submit their updates regularily - not timesheet, but just selected tasks after entering hours. And train your PMs to checking  Approval Center before making changes like this. If processes like submitting and approving are not used, system can't stop this kind of actions. At least not that I am aware of.

    Sorry!
    Barbara

    _______________________________________________________________________________
    To increase the value of this forum, please mark the replies that helped to solve your issue as answer. If you find answers to questions from other forum participants to be helpful, please mark them as helpful. Your participation will help others to find an appropriate solution faster.
    Thanks for your support!

    Wednesday, February 5, 2014 10:20 PM
    Moderator
  • Without protected actuals, as Barbara says, this is normal and expected behavior. In this case the timesheet record is still there. You can't blame Project Server for this. The fact that your PM leaves an active project checked out for extended periods of time for no reason is a behavior that you need to train your users not to do.

    Gary Chefetz, MCITP, MCP, MVP msProjectExperts
    Project and Project ServerFAQs
    Project Server Help BLOG

    Thursday, February 6, 2014 3:29 PM
    Moderator