TMGR: Dependency Incorrectly Reverses ID Scheduling Order (161649)
The information in this article applies to:
This article was previously published under Q161649 SYMPTOMS
Two tasks with the same Priority, a common person (or unassigned work), and
no dependency relationship to each other, may be incorrectly scheduled so
that the task with the smaller ID starts later than the task with the
larger ID.
CAUSE
This can happen if the task with the smaller ID is a successor of some
other task that has a person assigned to it. This causes the successor to
be scheduled as if it has a lower priority than specified.
WORKAROUND
Give the task that you want to schedule earlier a higher Priority, as
follows: - Click the Tasks tab and from the view banner list, select Task
Organizer.
- Select the task, and on the Edit menu, click Task Properties.
- In the Task dialog box, click the General tab, and from the Priority
list, select the desired priority. Click OK.
STATUS
Microsoft has confirmed this to be a problem in the products listed at the
beginning of this article. We are researching this problem and will post
new information here in the Microsoft Knowledge Base as it becomes
available.
MORE INFORMATION
Typically, when two tasks have no dependency relationship to each other,
but have a common person (or unassigned work), all other factors being
equal, the task with the smaller ID is scheduled earlier than the task with
the larger ID. However, the scheduling order may be incorrectly reversed if
the task with the smaller ID is given a predecessor with a person assigned
to it. The ID of the predecessor and the type of dependency doesn't matter.
If the dependency could have been satisfied without moving the task with
the smaller ID, then the reversal of the two tasks that have no dependency
relationship to each other is incorrect.
For example, if tasks Task1 and Task2 are entered in a new team file, with
ID numbers 1 and 2 respectively, and if person Bob is assigned to both,
then Task1 is automatically scheduled to start before Task2. If then task
Task3 with person Joe assigned is entered and specified as a predecessor of
Task1, with a Start-to-Start dependency, then Task1 and Task2 are scheduled
in reverse order, with Task1 starting after Task2. This happens even though
the dependency would have been satisfied without changing how Task1 and
Task2 were originally scheduled.
| Modification Type: | Minor | Last Reviewed: | 8/17/2005 |
|---|
| Keywords: | KB161649 |
|---|
|