Incorrect leveling when "Individual Assignments" check is off

[Magnus Hiie]

I'm having a problem when trying to use Project for very simple resource
leveling (for high level capacity planning). For that I'm using settings
where:
"Leveling order" is "ID only"
"Leveling can adjust individual assignments on a task" is off
"Leveling can create splits in remaining work" is on

An example illustrating th problem:
ID 1, Task A, Duration: 1 day, Resources: X
ID 2, Task B, Duration: 10 days, Resources: Y
ID 3, Task C, Duration: 5 days, Resources: X,Y
ID 4, Task D, Duration: 1 day, Resources: X
ID 5, Task E, Duration: 7 days, Resources: X

The problem is that after levelling Task D is scheduled to start 5 days
after Task A is finished, although resource X is available for these 5 days.
If I change Task C's duration, the gap changes accordingly, although Task C
is correctly scheduled much later.

The same thing also happens if I use the "Priority, Standard" leveling order
(with appropriate task priorities), and also with "Standard" order (although
with Standard, the resulting schedule is a little bit different".

The big problem with this is that the whole project is scheduled to take
longer than it actually should.

Is this a bug in Project or can somebody explain what am I doing wrong?

 

[Jan De Messemaeker]

Hi,

It is indeed a flaw of Project
I don't know whether this is an acceptable solution but whjen the X;Y task
has the lowest priority the thing works perfectly.
Hope this helps,

 

[Magnus Hiie]

Yeah, the problem is that most of the tasks have multiple resources assigned.
It took me a while to track down the case to such a simple example.

Regards,
Magnus