[taskjuggler] Re: reported effort vs. weeklymax limits

From: Chris Schlaeger (cs_at_kde.org)
Date: Sun Dec 18 2005 - 15:42:24 CET

• Next message: Tiberius: "[taskjuggler] one resource on multiple projects at the same time?"
• Previous message: Brian Mcminn: "[taskjuggler] reported effort vs. weeklymax limits"
• In reply to: Brian Mcminn: "[taskjuggler] reported effort vs. weeklymax limits"
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]

From: Chris Schlaeger <cs@kde.org>
Message-ID: <18ad.43a5754f@www.taskjuggler.org>
Date: Sun, 18 Dec 2005 15:42:24 +0100 (CET)
Subject: [taskjuggler] Re: reported effort vs. weeklymax limits

I'm afraid you hit a feature, not a bug. Bookings are meant to be exact reports of the time intervals where work has happened. As a concession to users we added the 'sloppy' attribute so that bookings could extend over the lunch break and vacations. But bookings are not scheduled. They are taken as they are.

I can understand that you don't want to enter all the work intervals manually. The user manual has a chapter called "Tracking the Project" that describes how to generate booking files. This way you can automatically generate bookings that also take your limits into account.

The same method is also described in the "http://www.taskjuggler.org/download/TaskJuggler-Workshop.sxi".

Hope that helps,
Chris

--
TaskJuggler Developer
-- 
To unsubscribe, email the address listed in the List-Unsubscribe header
For additional commands, email: taskjuggler-help@suse.com

• Next message: Tiberius: "[taskjuggler] one resource on multiple projects at the same time?"
• Previous message: Brian Mcminn: "[taskjuggler] reported effort vs. weeklymax limits"
• In reply to: Brian Mcminn: "[taskjuggler] reported effort vs. weeklymax limits"
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]

This archive was generated by hypermail 2.1.7 : Sun Dec 18 2005 - 15:42:27 CET