Priority/leveling issue

[go83]

I have a small issue getting tasks to order properly using Priority
Standard leveling. Here's my case, which involves the same resourc
working on two different projects. I am leveling by inserting bot
projects (common resource pool) into a single file.

Project A (Project level priority 500)

Task 1 for Resource A, Task Priority 550, partially complete

Project B (Project level priority 500)

Task 2 for Resource A, task Priority 500, not started

When I level, Project schedules Task 2 ahead of the completion of Tas
1. How could this be

 

[Guest]

I have a small issue getting tasks to order properly using Priority,
Standard leveling. Here's my case, which involves the same resource
working on two different projects. I am leveling by inserting both
projects (common resource pool) into a single file.

Project A (Project level priority 500)

Task 1 for Resource A, Task Priority 550, partially complete

Project B (Project level priority 500)

Task 2 for Resource A, task Priority 500, not started

When I level, Project schedules Task 2 ahead of the completion of Task
1. How could this be?

It's been a while since I checked the factors influencing resource
leveling, but last time I did, they included Total Slack, placement in the
list of tasks, and others. Priority, Standard leveling only move Priority
to the first on the list, but the others are still there. You might try
upping the Task 1 priority to see if that helps.