From: h_hettema (h_hettema_at_gmx.net)
Date: Sat Jan 14 2006 - 21:16:12 CET
From: h_hettema <h_hettema@gmx.net> Message-ID: <18fd.43c95c0b@www.taskjuggler.org> Date: Sat, 14 Jan 2006 21:16:12 +0100 (CET) Subject: [taskjuggler-devel] Re: Booking spent efforts and efforts to finish a task
This topic addresses the same problem I have with bookings: I have to specify exact times, while at our company we make bookings at week-level, thus having the totals available after the week.
One possible way to solve this perhaps would be to implement the following:
booking time-1 time-2 task1 { sloppy 2 }
booking time-3 time-4 task2 8h
booking time-5 time-6 task1 16h
The first is the normal booking as currently implemented. The second and third just specify the amount of hours worked in the given time-interval on a task. By definition such a booking should perhaps be { sloppy 2 } or above (implicit rule).
After all bookings have been made, but before scheduling, the "free booking hours" (that is, the second and third rule above) are allocated to the non-booked hours in a working-week for the given resource. Since the hours are specified in a period, the exactness of the booking is not critical, thus this can be done.
After this booking allocation, scheduling can resume as it was.
Checking that the hours fit in a week (a person cannot work more than 24 hours on a day) and similar tests can be added. This way bookings, which I now have to artificially allocate in given intervals, can be adapted to the way I normally handle total hours over a week.
Is this in your opinion feasible? As far as I understand the code, I think it can be done. I could look at this modification (but I first would like a bit of feedback on the idea).
Hindrik
-- 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 : Sat Jan 14 2006 - 21:16:14 CET