![]() |
|
#1
|
|||
|
|||
|
Hi All, new member to the forum, so thanks in advance for reading my query
I have noticed if you change a batch of tasks to update the resource, then level those tasks, MSP schedules the longest task first. I list my tasks in chronological order so I'd like levelling to consider this when assigning tasks to the same resources Once I level some tasks I'd also like that to be 'locked down' and if I assign tasks to someone further down the plan I'd like levelling to ignore the batch above (I understand I can use dependencies for this, but that's a hack) |
|
#2
|
|||
|
|||
|
Quote:
Great forum, thanks |
|
|
|
Similar Threads
|
||||
| Thread | Thread Starter | Forum | Replies | Last Post |
| Auto scheduling issue - longest task first? | Project_64 | Project | 3 | 01-25-2016 01:14 PM |
MS Project Resource Capacity and Auto-levelling
|
Senor_Babs | Project | 2 | 11-01-2014 02:46 PM |
Levelling resource's units to calculate duration task
|
codeghi | Project | 10 | 03-01-2014 08:13 AM |
Mid-Task resource scheduled 0 hours increasing task duration needlessly
|
DarlaWeber | Project | 1 | 01-31-2014 02:30 PM |
MS Project - Maximizing resource levelling
|
aguatorito | Project | 3 | 03-10-2013 06:08 AM |