From: Lutz Vieweg (lkv_at_isg.de)
Date: Tue May 06 2003 - 19:02:52 CEST
Message-ID: <3EB7EABC.9030103@isg.de> Date: Tue, 06 May 2003 19:02:52 +0200 From: Lutz Vieweg <lkv@isg.de> Subject: [taskjuggler] timingresolution bug
Hi,
the following test project demonstrates a problem
with smaller "timingresolution" values:
--------------------------------------------------
project test "test" "0.1" 2003-05-01 2003-07-30 {
now 2003-05-01
timingresolution 12 min
dailyworkinghours 8
}
resource harry "harry"
task work1 "work1" {
start 2003-05-02
effort 2d
allocate harry
}
htmlresourcereport "test.html" {
sortresources sequenceup
columns name, daily, effort
hidetask 0
loadunit hours
}
--------------------------------------------------
Instead of taking 2 working days, the task
is scheduled to take 2 days + 12 minutes (0.2 hours).
The unit passed to "effort" doesn't matter, the
same happenes e.g. for "effort 16h".
Maybe some sort of rounding/precision problem?
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 : Tue May 06 2003 - 20:03:14 CEST