|
Prev: Changing Start and Finish Dates
Next: Is there a way to mass set resource units to a specific percentage
From: walkema on 21 May 2008 14:50 Microsoft Project 2003 documentation states that a task with Priority = '1000' will not be resource leveled. So I assigned a Priority = '1000' on some tasks I do not want delayed by resource leveling. When I resource leveled, it delayed these tasks even though their priority = '1000', whether I used 'Priority, Standard' or just 'Standard' for Leveling Order. How do I prevent resource leveling from delaying these tasks?
From: Jack Dahlgren on 21 May 2008 15:06
Walkema, I can not reproduce your problem in Project 2003. In both Standard and Priority Standard the leveling does not move those tasks nor any of their predecessors. Did you clear the leveling after you set the priority to 1000? Try creating a small sample plan and trying it. -Jack Dahlgren "walkema" <walkema(a)discussions.microsoft.com> wrote in message news:8BBC00AA-4FBE-44D4-B2B9-E323880F5C0F(a)microsoft.com... > Microsoft Project 2003 documentation states that a task with Priority = > '1000' will not be resource leveled. So I assigned a Priority = '1000' on > some tasks I do not want delayed by resource leveling. When I resource > leveled, it delayed these tasks even though their priority = '1000', > whether > I used 'Priority, Standard' or just 'Standard' for Leveling Order. How do > I > prevent resource leveling from delaying these tasks? |