Best practise for priority values

S

SoftwareTester

Are there any "rules" (common practises) for using certain values while
specifying priority of a task?
 
D

Dale Howard [MVP]

Software Tester --

The task Priority field is used for only one purpose: leveling
overallocated resources. The system sets the Priority number at 500 (Medium
priority) on every task by default. You can set the Priority number range
on any task from 0 to 1000, where 1000 means Do Not Level. If you want to
use task Priority numbers with leveling overallocated resources, you can
first examine your overallocations in the Resource Usage view, and then set
Priority numbers on the tasks that contain overallocated resources in any
task View, such as the Gantt Chart view. The key is to make sure that there
are NO duplicate Priority numbers on the tasks with overallocated resources.

Also, in the Resource Leveling dialog, you should also select the "Priority,
Standard" option in the Leveling Order pick list to force the system to
consider the task Priority number first in its leveling algorithm. Hope
this helps.
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Top