While providing task end date manualy, it would be
usefull to auto calculate the number of ideal days before
completion. todo = working days(end - start)/LF
Well, the problem is, not all users want that behaviour.
Actually, if you really want this, the current solution is
to set the todo field instead and the date will be
calculated... I know it's not the same, but the "manual end
date input" has been added for the situation where you want
it to be "unlogical" compared to todo field... that's what
you uncheck "calculated"...
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
- I choose a start date
- I set "todo" field
=> the end date is automatically calculated (with the
expression you gave: end date = start date + todo * LF)
Then if you want to set another end date (so, not the
automatically calculated value), then you uncheck
"calculated", and the value becomes what I call "unlogical".
Basically this can be useful if there is an exceptional day
off, for example, that is not handled by the "holiday"
option of XPWeb.
For example, start date is today which is monday, todo is 3
and LF = 1. End date should be Wednesday. But you know
tomorrow will be full for meeting... then you add one day by
setting the end date manually to Thursday...
If you have other solutions for these cases, feel free to
discuss it!
Olivier
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Ok, I understand. So my proposal is a bit another thing. Set
end date and calculate todo with pressing new button. In
this case end date works like deadline for the task, so user
doesn't need to adjust todo manualy.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
That's an interesting idea (basically, you'd _choose_
between setting todo _or_ end date manually).
The only this is this:
- end date is actually calulated from start date _if_ the
start date is "after today". If start date is in the past,
then end date = _today_ + todo * LF. To summarize, end date
= max(start date, today) + todo * LF.
If todo is calculated from end date, then as today "moves"
in time, what happens to todo? I suppose it decreases...
without "done" being changed... What do you propose for that?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Actually, I am not fond of full-auto calculation of todo. But in
general, it could be an interesting option to try. I propose to
add the button which manually calculate todo = max(1, pace
(manual-end-data-today) / LF). Considering button+box for
end date, you could try add box for full-auto too. This will
require some method to make the task to be "DONE". I think
full auto-todo introduces the way of thinging in tearms of
deadline, not XP ideal days.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Logged In: YES
user_id=633898
Well, the problem is, not all users want that behaviour.
Actually, if you really want this, the current solution is
to set the todo field instead and the date will be
calculated... I know it's not the same, but the "manual end
date input" has been added for the situation where you want
it to be "unlogical" compared to todo field... that's what
you uncheck "calculated"...
Logged In: YES
user_id=410460
Could you give an example of "unlogical" usage? I don't
quite understand.
Logged In: YES
user_id=633898
Basically, the "logical" usage is:
- I choose a start date
- I set "todo" field
=> the end date is automatically calculated (with the
expression you gave: end date = start date + todo * LF)
Then if you want to set another end date (so, not the
automatically calculated value), then you uncheck
"calculated", and the value becomes what I call "unlogical".
Basically this can be useful if there is an exceptional day
off, for example, that is not handled by the "holiday"
option of XPWeb.
For example, start date is today which is monday, todo is 3
and LF = 1. End date should be Wednesday. But you know
tomorrow will be full for meeting... then you add one day by
setting the end date manually to Thursday...
If you have other solutions for these cases, feel free to
discuss it!
Olivier
Logged In: YES
user_id=410460
Ok, I understand. So my proposal is a bit another thing. Set
end date and calculate todo with pressing new button. In
this case end date works like deadline for the task, so user
doesn't need to adjust todo manualy.
Logged In: YES
user_id=633898
That's an interesting idea (basically, you'd _choose_
between setting todo _or_ end date manually).
The only this is this:
- end date is actually calulated from start date _if_ the
start date is "after today". If start date is in the past,
then end date = _today_ + todo * LF. To summarize, end date
= max(start date, today) + todo * LF.
If todo is calculated from end date, then as today "moves"
in time, what happens to todo? I suppose it decreases...
without "done" being changed... What do you propose for that?
Logged In: YES
user_id=410460
Actually, I am not fond of full-auto calculation of todo. But in
general, it could be an interesting option to try. I propose to
add the button which manually calculate todo = max(1, pace
(manual-end-data-today) / LF). Considering button+box for
end date, you could try add box for full-auto too. This will
require some method to make the task to be "DONE". I think
full auto-todo introduces the way of thinging in tearms of
deadline, not XP ideal days.