From: Chris Schlaeger (cs_at_kde.org)
Date: Mon Dec 05 2005 - 21:57:18 CET
From: Chris Schlaeger <cs@kde.org> Message-ID: <188b.4394a9ae@www.taskjuggler.org> Date: Mon, 5 Dec 2005 21:57:18 +0100 (CET) Subject: [taskjuggler] Re: How to interleave small task inside a big project
Wow, it took me a bit to decode this project. ;)
The reason why you get this surprising behaviour is the mixture of ALAP and ASAP tasks in combination with different priorities. The scheduler does work the tasks down starting with the top priority. But it cannot strictly work down the priorities when higher prio ASAP tasks are blocked by lower prio ALAP tasks.
In your case the Release Note tasks is turned into such a blocker when you set the priority below 700. Then it's pushed out beyond your maxends as it fights with the long runners Specification and Software development about dev1.
So I have 2 recommendations:
Try avoid mixing ALAP and ASAP tasks. Either schedule the tasks from start to end or (less common) from end to start. Avoid mixing 'depends' and 'precedes' tasks.
The 'maxends' cause errors and prevent the reports from being displayed. I will turn those into warnings with the next version so you can see what is going on. Until then you have to comment out the offending 'maxends' to get the reports.
Chris
-- TaskJuggler Developer -- To unsubscribe, email the address listed in the List-Unsubscribe header For additional commands, email: taskjuggler-help@suse.com
This archive was generated by hypermail 2.1.7 : Mon Dec 05 2005 - 21:57:21 CET