locked
What permissions are required to allow our Team Leads to un-assign and re-assign tasks RRS feed

  • Question

  • Hi,

    Our leads need to be able to re-assign their direct reports into different tasks.  Currently the PM does everything, but we are trying to move off some of the workload around this.  We still want the PM to be the only one able to publish.

    Is there a way to do this without making them the Project Owners?

    Thanks

    (we are running Server 2010)

    • Edited by Scott_CF Friday, April 5, 2013 1:01 AM formatting
    Friday, April 5, 2013 12:59 AM

Answers

  • Scott, there is not a built-in function that will do precisely what you want, but you can get close using the security model.  You say you only want the owner to be able to publish the project.  That is definitely possible.

    I hope you understand Project Server security, because the following is a short-hand description of what you need.

    You need an RBS defined in which Team Leads are above Team Members.

    You need a Category in which the members have permission to projects on which their RBS descendants are resources, and resources who are direct descendants of the user. 

    The Category permissions should include Create new task or assignment, Open project, and Save project to Project Server.


    Reid McTaggart – DeltaBahn Vice President
    Blog | Twitter | LinkedIn Please click Mark As Answer; if a post solves your problem or Vote As Helpful if a post has been useful to you. This can help other community members reading the thread.

    • Marked as answer by Scott_CF Monday, April 15, 2013 6:29 PM
    Tuesday, April 9, 2013 2:48 PM

All replies

  • Have you look at using the "Reassign Task" permission in the General settings.


    Michael Wharton, MVP, MBA, PMP, MCT, MCTS, MCSD, MCSE+I, MCDBA
    Website http://www.WhartonComputer.com
    Blog http://MyProjectExpert.com contains my field notes and SQL queries

    Friday, April 5, 2013 1:42 PM
  • Correct, you can use Reassign Task global permission

    This will allows a user (Lead) to delegate an assigned task to another (existing) user. Grant this permission to members of your organization who need the ability to delegate task assignments to other resources. For example, a large project may be run by a single project manager, but actually implemented by several teams, each with their own team lead. A project manager could assign the team leads in the project plan, and then the team leads could in turn delegate each task to individual members of their teams. This example creates an additional layer of task management within the larger organization, but it can also simplify resource allocation within projects themselves and make it easier for a project manager to manage large projects. Or, if you have a resource that is about to leave on a three-week vacation, and this resource had this permission, they would be able to assign their tasks directly to other resources instead of having the project manager check out the project and reassign resources.

    Hope this will help you. 

    -----------------------------------------------------------------------------------------------------------

    Raushan Kumar  | LinkedIn
    Please click Mark As Answer if this post solves your problem or Vote As Helpful if a post is useful to you. This will be useful to other community members following the thread.

    • Proposed as answer by Prachi R Sunday, April 7, 2013 7:44 AM
    Friday, April 5, 2013 2:23 PM
  • I had looked into "reassign Task" but found that it only applies to tasks that are already assigned to you. 

     I am looking for Lead A to be able to move an assignment from User B to User C.  The task was never assigned to Lead A in the first place.

     

    thank you for your replies!

    Friday, April 5, 2013 5:01 PM
  • Scott, there is not a built-in function that will do precisely what you want, but you can get close using the security model.  You say you only want the owner to be able to publish the project.  That is definitely possible.

    I hope you understand Project Server security, because the following is a short-hand description of what you need.

    You need an RBS defined in which Team Leads are above Team Members.

    You need a Category in which the members have permission to projects on which their RBS descendants are resources, and resources who are direct descendants of the user. 

    The Category permissions should include Create new task or assignment, Open project, and Save project to Project Server.


    Reid McTaggart – DeltaBahn Vice President
    Blog | Twitter | LinkedIn Please click Mark As Answer; if a post solves your problem or Vote As Helpful if a post has been useful to you. This can help other community members reading the thread.

    • Marked as answer by Scott_CF Monday, April 15, 2013 6:29 PM
    Tuesday, April 9, 2013 2:48 PM
  • Hello Reid,

    I see that Scott_CF confirmed your guidance as the correct answer. Team Lead is reassigning work from User A to User B, but the task was never assigned to the Team Lead to begin with. I don't see the Reassign option when viewing team tasks in resource assignments.

    Here's a scenario, I know that I need a Propulsion Specialist (User A) and Avionics Specialist (User B) for different tasks, but I don't know which named specialists will be assigned. So, the PM (me) uses a Generic Resource (e.g. PropulsionSME, AvionicsSME). If I just assign these tasks to a team lead, I lose how much of each resource is required. I'd like to assign to the right resource placeholders, but let the Lead reassign.

    How do I assign the tasks to a generic resource (or non-generic), but have the Team Lead able to reassign the work?

    Where does the Team Lead see all tasks assigned to his / her team members and have ability to reassign?


    WashDC

    Friday, July 31, 2015 8:01 PM