none
Project server 2013, time sheet manager setting, Can PM manage own staff's time sheet? RRS feed

  • Question

  • Hi there,

    I set PM as timesheet manager for his members.  While a guy join 2 projects with 2 PM, can I do the setting for his timesheet owner, such like:

    Task 1 in Prj A approved by PM A

    Task 2 in Prj B approved by PM B 

    In resource setting , only 1 timesheet manager can be set.  Can timesheet manager selected by Project?

    Any advise? 


    Jou Chen


    • Edited by Jou Chen Tuesday, April 28, 2015 9:51 AM
    Tuesday, April 28, 2015 9:51 AM

Answers

  • It has to be done just once Jou Chen, not for every new task.

    Basically, if you first created the project, the next steps have to be performed in order to transfer the project ownership to the new PM:

    1. In PWA, open the project détails from the project center and update the project owner. Eventually, add it to the project team.
    2. In MS Project Pro, the new owner has to insert the status manager column and add himself to all tasks and publish the project in order to set him as the approver for task updates.

    Once those steps done, there is nothing more to do, just running the project execution. When the PM will created new tasks or update existing tasks, he will be the status manager automatically, so he won't new to do the steps again. This is just a "one shot" operation at project creation.


    Hope this helps,


    Guillaume Rouyre, MBA, MVP, P-Seller |

    • Marked as answer by Jou Chen Thursday, May 28, 2015 8:33 AM
    Wednesday, April 29, 2015 7:37 AM
    Moderator
  • Hi Jou,

    1- You cannot do it on behalf of the PM. He has to do it by himself. It is not a free text field but a drop down menu with names. You'll see just the former and current status managers of the project and the current user. This is why you cannot do it yourself.

    That being said, recently there was a discussion on LinkedIn about an approach with category/group settings which might allow an admin to set the status manager on behalf of another user but I haven't tested it.

    2- After the new PM correctly updates himself as the new status manager, it should be ok. Or maybe publish and close the project and reopen it. 


    Hope this helps,


    Guillaume Rouyre, MBA, MVP, P-Seller |


    Wednesday, April 29, 2015 10:26 AM
    Moderator

All replies

  • Hi Jou Chen,

    Are you using the Single Entry Mode?

    You have to differenciate the status owner (project manager) from the timesheet manager (resource manager).

    The status owner is generally the project owner, but it can be defined at task level in the project plan. The status manager will be the one receiving the task update for approval. Thus tasks in Project A will be approved by PM A while tasks in Project B will be approved by PM B.

    Now talking about the timesheet, it is sent to one unique timesheet manager, which is defined only at resource level. Meaning that a resource can only have 1 timesheet manager and it cannot be set for a project or for a task.


    Hope this helps,


    Guillaume Rouyre, MBA, MVP, P-Seller |

    Tuesday, April 28, 2015 10:29 AM
    Moderator
  • Hi Guillaume Rouyre,

    You mean that Project Owner is the PM and status owner, he can receive all the task status update.  But now my situation is I set PM H as the project Owner , but I  (admin) always receive the task update information.  

    What happened ?


    Jou Chen

    Wednesday, April 29, 2015 2:40 AM
  • Hi Jou Chen,

    This is probabbly because you created the project. The project Creator is by default the status manager. Evenif you update the project owner, it doesn't change the status manager. The new PM has to open the project, insert the status manager column and update the value for ALL tasks to his name. You cannot do it for him. Then he has to publish the project and he will receive all project's tasks updates.


    Hope this helps,


    Guillaume Rouyre, MBA, MVP, P-Seller |

    Wednesday, April 29, 2015 5:55 AM
    Moderator
  • No matter new tasks or exist tasks, new PM should add status manager manually, am I right?

    It seems a little strange.


    Jou Chen

    Wednesday, April 29, 2015 6:27 AM
  • It has to be done just once Jou Chen, not for every new task.

    Basically, if you first created the project, the next steps have to be performed in order to transfer the project ownership to the new PM:

    1. In PWA, open the project détails from the project center and update the project owner. Eventually, add it to the project team.
    2. In MS Project Pro, the new owner has to insert the status manager column and add himself to all tasks and publish the project in order to set him as the approver for task updates.

    Once those steps done, there is nothing more to do, just running the project execution. When the PM will created new tasks or update existing tasks, he will be the status manager automatically, so he won't new to do the steps again. This is just a "one shot" operation at project creation.


    Hope this helps,


    Guillaume Rouyre, MBA, MVP, P-Seller |

    • Marked as answer by Jou Chen Thursday, May 28, 2015 8:33 AM
    Wednesday, April 29, 2015 7:37 AM
    Moderator
  • Yes thats true every Status manager has to for the first time assign himself as a status manager for one of the tasks & publish the plan. No one can on do this on his/her behalf this for the first time. Once this is done then his/her name will be available in the drop down moving forward and then can be changed by the PM/Admin.

    Yet to get a clarity on the reason for these functionality to really understand its applicability & benfits.

    Wednesday, April 29, 2015 7:51 AM
  • Yes, this is my question mark.

    During project, for some reason, we change the PM, what I do is update Project owner in PWA--project details--project owner. But in your mind, the status owner is still the old one.  He face 2 needs,

    1. Update the exist task's status manager, it's OK for me.
    2. When he add new task, he must add  status owner every time , this bother me.

    Jou Chen


    • Edited by Jou Chen Wednesday, April 29, 2015 9:36 AM
    Wednesday, April 29, 2015 9:36 AM
  • Your point 1 is correct.

    Your point 2 is NOT. Once he did it for all the existing tasks, when he will create a new task, he will NOT have to update the status manager on the new task. Project will recognize who is creating the task and set him automatically as the task's status manager.


    Hope this helps,


    Guillaume Rouyre, MBA, MVP, P-Seller |

    Wednesday, April 29, 2015 9:41 AM
    Moderator
  • Hi Guillaume Rouyre,

    A new question about point 1 ,  I want to do the action like Point 1.  I add status manager column in Task Schedule.

    New PM login PWA, while he want to update status manager, the column cannot be write, am I miss some steps?

    I tested Point 2,  new PM create a new task, but the status manager is still me. Any advise? 

    /Jenny 


    Jou Chen

    Wednesday, April 29, 2015 10:07 AM
  • Hi Jou,

    1- You cannot do it on behalf of the PM. He has to do it by himself. It is not a free text field but a drop down menu with names. You'll see just the former and current status managers of the project and the current user. This is why you cannot do it yourself.

    That being said, recently there was a discussion on LinkedIn about an approach with category/group settings which might allow an admin to set the status manager on behalf of another user but I haven't tested it.

    2- After the new PM correctly updates himself as the new status manager, it should be ok. Or maybe publish and close the project and reopen it. 


    Hope this helps,


    Guillaume Rouyre, MBA, MVP, P-Seller |


    Wednesday, April 29, 2015 10:26 AM
    Moderator