Re: [taskjuggler-users] how to handle tasks done 'to soon'

128 views
Skip to first unread message

Bas de Bruijn

unread,
May 15, 2013, 11:43:36 AM5/15/13
to taskjugg...@googlegroups.com
Hi Peter,
In the scenario you use for bookings (your tracking scenario) you should adjust the effort to the effort it has become. Then when the time that has been spent matches the effort your task is considered 'done'.
Regards,
Bas

On 15 mei 2013, at 12:39, Peter De Cleyn <peter....@gmail.com> wrote:

Hi list,

I'm trying to implement TJ in our team and so far I'm quite happy with it but can't seem to figure out how to handle tasks which were done faster than planned.

I'm using bookings and have a tracking scenario and I regularly freeze the project. On such speedy tasks, some bookings were made and it was also marked as complete 100, even on both scenarios. TJ however keeps scheduling time for this task. 

I could of course change the original effort estimate to match the work done, but then I loose track of the original planning. I though the tracking scenario was used to cope with changes along the way, but it seems to me it only covers delay (which is unfortunately more like reality in some cases ;-) )

Any hints on how to tackle this?

regards,

Peter

--
You received this message because you are subscribed to the "TaskJuggler Users" group.
To post to this group, send email to taskjugg...@googlegroups.com
To unsubscribe from this group, send email to
taskjuggler-us...@googlegroups.com
For more information about TaskJuggler visit http://www.taskjuggler.org
---
You received this message because you are subscribed to the Google Groups "TaskJuggler Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to taskjuggler-us...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
 
 

Luca Castelluzzo

unread,
Jun 13, 2013, 3:38:40 AM6/13/13
to taskjugg...@googlegroups.com
Hi Peter and Bas,

In TJ2 I used to mark the unexpectedly quick tasks as "scheduled". This way the scheduler didn't try to re-schedule these tasks at all and the reports only took into account the bookings.

Unfortunately, in TJ3 the "scheduled" attribute doesn't appear to work the same way because when I use it, TJ throws this error:

Error: Task <taskname> is marked as scheduled but does not have a fixed start and end date.

If I add a start date and an end date it looks working, but this is such a waste of time... 

Do you think that this should be reported as a bug?


Regards,
Luca

Chris Schlaeger

unread,
Jun 13, 2013, 11:22:07 AM6/13/13
to taskjugg...@googlegroups.com
You probably haven't marked the scenario as tracking scenario. See http://www.taskjuggler.org/tj3/manual/trackingscenario.html

Chris


Peter De Cleyn

unread,
Jun 14, 2013, 9:28:10 AM6/14/13
to taskjugg...@googlegroups.com, ch...@linux.com
I indeed forgot to define the tracking scenario.

thx!

Peter

Op donderdag 13 juni 2013 17:22:07 UTC+2 schreef Chris Schlaeger het volgende:
Reply all
Reply to author
Forward
0 new messages