g3tq-jcrq_at_dea.spamcon.org
Date: Thu Jun 19 2003 - 10:24:36 CEST
Message-Id: <200306190824.h5J8OaJ22667@localhost.localdomain> From: g3tq-jcrq@dea.spamcon.org Date: Thu, 19 Jun 2003 10:24:36 +0200 Subject: [taskjuggler] minstart
Hello !
Once the project plan is established, adding unexpected tasks and in general
doing some shuffling is quite hazardous. Things that were in the past (and
were done) may be shifted in the future, and vice-versa just by adding a
couple items or changing a resource in some (future) task.
What is the best recommended way of handling this ?
Part [A]: Here is how I handle it, but maybe other poeple have other input.
Part [B]: Some technical issues.
Part [C]: Another idea (for a tool ?)
[A] My current practice is that I export a "milestones" file of all
milestones. Once in a while I copy milestones into "milestones.tjsp" which
gets included in the main project. Before commiting (CVS) all my tjsp files,
I verify that milestones have not shifted outrageously as a result of my
changes. Is some respects, I keep a "baseline" or a "snapshot" from before
and after my modifications, and I compare the shiftings manually.
Any suggestions on how to live with evolutions and how other people manage are
VERY welcome !
[B] My most recent practice to fine-tune the tasks is to add them with a given
"start" date that is in the future (from the day I add them). This works
fine, but restricts the algorithms too much. I tried to add "minstart"
instead, and here is what I get:
119: Plan start time of task photo.backup.check is too early
Date is: 2003-06-05-14:00:00-CEST
Limit is: 2003-06-11-00:00:00-CEST
What goes wrong ?
To reproduce this, here is the structure:
#######################################
project qmmdev "Main" "$Id" 2003-05-20 2004-02-31 {}
[...]
task myChapterTask {
start 2003-05-20
[...]
task backup "Backups" {
minstart 2003-06-11
priority 300
task check "Meeting to check all is OK" { effort 4h allocate ab }
}
}
#######################################
[C] To "freeze" what is now from the past, and avoid changing the past when
you modify the project, maybe it would be a good idea to:
- export all tasks
- find which are from the past
- replace the tasks in the project file with their "planscheduled"
counterpart from the export.
A perl tool could probably do this.
Would this solve the issue ? I see one problem : if a resource has some spare
time in the past, this method won't forbid that the new task I add will be
planned using that slack time....
Thanks for all, floks ! this is the best open source project planner that I
have found. Keep focusing on the algorithmics, not on the GUI !
Marcel.
-- 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 Jun 23 2003 - 09:58:50 CEST