Hi,


I have seen below behaviour:
- A task A got split as there were some actuals before the start date followed by a work done on a different task
-Later there was a changing in project priorities with other project tasks getting higher priorities
- To make sure that half worked task A gets finished before any other task I set its priority to 1000
-Still pending part (after the split) of task A is prioritised after all the tasks having priority less to it! (I use Priority/Standard levelling; no splits allowed)
Why is that? To get around I had to delete actuals for Task A and then re-level.
thanks

see my answer in the other forum:

http://tek-tips.com/viewthread.cfm?qid=1675858

To make it simpler to explain, lets take a look at the example I have attached. Tasks 4 to 1 have decreasing priority however due to some reason (common in IT projects), developer thought its smarter to work on some part of task 1 first. hence actuals got recorded for task 1 (typically actuals are recorded twice/thrice a week but full review of tasks happens only once a week as there are 100's). Now when its realised that lets get over with Task1 completely - its too late: even if you change priority of task 1 to 1000 it will not delete the split.

Attached Files

Pending_part_of_split.zip (39.9 KB, 11 views)

Answer at:

http://tek-tips.com/viewthread.cfm?qid=1675858