[taskjuggler] bug? - task "length" not really honoured ?

From: Lutz Vieweg (lkv_at_isg.de)
Date: Sat May 03 2003 - 00:40:33 CEST 

Message-ID: <3EB2F3E1.3070101@isg.de>
Date: Sat, 03 May 2003 00:40:33 +0200
From: Lutz Vieweg <lkv@isg.de>
Subject: [taskjuggler] bug? - task "length" not really honoured ?

Hi,

I wondered how something could be done so fast in my real project,
and I broke down the problem to the following test scenario:

-------------------------------------------------------------
project test "test" "0.1" 2003-05-01 2003-05-30 { now 2003-05-01 }

resource harry "harry" { vacation 2003-05-05 - 2003-05-30 }

resource hugo "hugo"

task work1 "work1" {
        start 2003-05-02
        length 10d
        allocate harry
}

task work2 "work2" {
        depends !work1
        duration 10d
        allocate hugo
}

htmlresourcereport "test.html" {
   sortresources sequenceup
   columns name, daily, effort
   hidetask 0
   loadunit hours
}
-------------------------------------------------------------

Mysteriously, the resulting project plan suggests the work will
be done during may - even faster than it would have been possible
if harry did not go on vacation.

It seems the "length 10d" attribute of "work1" is simply ignored.
If it wasn't the project should not be possible to do during may.

Any ideas?

Regards,

Lutz Vieweg 

-- 
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 : Sat May 03 2003 - 00:41:33 CEST