From: bjvest (bjvest_at_post.cybercity.dk)
Date: Sun Feb 19 2006 - 18:24:19 CET
From: bjvest <bjvest@post.cybercity.dk> Message-ID: <1987.43f8a9c3@www.taskjuggler.org> Date: Sun, 19 Feb 2006 18:24:19 +0100 (CET) Subject: [taskjuggler-devel] scheduling policy cross-talk between scenarios
Some of the scenario specific properties like start and end implicitly set the scheduling policy. The scheduling policy, however, does not seem to be specific to a scenario. Rather, once a scheduling policy is set for a task, it seems that it applies to all scenarios. Hence, if I have two scenarios - "planned" and "actual" - and insert actual:end and actual:start (in that order), then ASAP scheduling will be applied for both the "planned" and the "actual" scenarios.
I would have expected that once I had made my plan in the "planned" scenario, and subsequently started on the project and the tracking of the tasks within the "actual" scenario, the "planned" scenario would be left untouched by the task tracking in the "actual" scenario.
How about making the scheduling policy scenario dependent? Properties like "depends" and "precedes" could perhaps be made to set a default scheduling for all scenarios. This default scheduling could then be overridden by scenario specific properties like "scheduling", "start", and "end".
The difficult part of the proposed change is probably to make the input file and report changes backwards compatible.
Comments?
-- To unsubscribe, email: taskjuggler-devel-unsubscribe@suse.com For additional commands, email: taskjuggler-devel-help@suse.com
This archive was generated by hypermail 2.1.7 : Sun Feb 19 2006 - 18:28:40 CET