Re: [O] [PATCH] Smart inference of task progress when exporting to TJ3

[Martin Becker]

Hi Christian,

> I like this patch, this is good stuff. Can you tell me how you use
> this?
Thanks, I attached a file where I made some tests. My idea was, that clock times are only used when there is no explicit information given, viz., when there is neither a property `complete' nor the task state equals "done". Since I am clocking most of my activities, it would be convenient for me to let the exporter/TJ3 infer the task progress instead of explicitly giving the `complete' property. So far for the story.

> I.e. does tj3 adapt the length fo a task based on your clock
> table?
No, TJ3 is not adapting anything here, neither am I. Since you cannot give values > 100 (%), my patch limits the maximum inferred progress to 99. We could let the exporter overwrite the effort with the clocksum in those cases, but it doesn't seem right.
I found out some more details after reading the documentation of TJ3:
- The `complete' property is merely for documentation purposes, it's totally ignored by TJ3 when it comes to scheduling. It just "looks nice". Being only "cosmetic", tracking can be done via clock times as proposed.
- But there is another thing we could do: One can add "bookings" to the tasks, which could be exactly the clock times from org-mode. I tried this manually and it seems to be a mixed blessing: If doing so, TJ3 internally grows the effort when the bookings exceed them and reschedules accordingly (which is nice). On the other hand sensible clock times are vital then. What I mean is, when there are bookings that are too early w.r.t. a task's earliest possible start (due to dependencies etc.), then TJ3 exits with an error. I am not sure this is wanted behavior. What do you think? Additionally, the visually attractive completeness is not derived from the bookings or anything.

> I would write this using cond instead of nested if. Makes it more
> clear.
Oh yes, I will do that. I am fairly new to Lisp, it is a nice exercise.

>>> 2. IIUC you don't need the TINYCHANGE cookie because the changes
>>> are made in contrib/ which doesn't require copyright assignment.
> The taskjuggler exporter used to be in core before it was moved to
> contrib by Bastien or Nicolas on the bases that there aren't many
> users (and probably because it wasn't maintained very well). This is
> OK for now, but eventually I'd like to move it back to core. So we
> need assignment for this patch.
Is it that I need to sign something? That is not a problem, I happily contribute here.

tj3test.org
Description: Text document