Summary: | Percent completed not handled right with subtasks | ||
---|---|---|---|
Product: | [Applications] korganizer | Reporter: | Michael J. Korman <mike> |
Component: | general | Assignee: | Cornelius Schumacher <schumacher> |
Status: | RESOLVED DUPLICATE | ||
Severity: | wishlist | ||
Priority: | NOR | ||
Version: | 3.2.1 | ||
Target Milestone: | --- | ||
Platform: | unspecified | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: |
Description
Michael J. Korman
2004-05-03 08:40:34 UTC
On Monday, 03. May 2004 08:40, Michael J.Korman wrote:
> In my opinion, subtasks should be completely bound to the supertasks.
> Changing one should modify the other accordingly.
But then you can't have hierarchies any more where your supertask involves
more than each of the subtasks accumulated. E.g. take cooking a meal:
[ ] cooking dinner tonight
[ ] shopping: whatever you need
[ ] Ask for the time
[ ] Does your better half like the food?
Surely, you won't put in a subtask "[ ] cook the dinner", and you don't want
the task marked finished when you have checked everything before you do the
actual cooking. However, when you're finished with cooking, you just check
the superitem, and all subitems are also finished.
Another sitation in which you don't want the supertask to be bound to the
subtasks is if you categorize your todos visually:
[ ] KDE
[ ] KOrganizer
[ ] fix bug XXX
[ ] implement that new feature
[ ] Check if korg really crashes in that situation
[ ] KPilot
[ ] Conduit so and so does not behave.
The KDE, KOrganizer and KPilot supertasks should never be checked, because in
the future you'll have new items there.
Now, the latter case should probably be implemented via uncheckable entries in
the todo list, but that's not possible yet, so completely binding subtodos
with their supertodos is suboptimal.
Cheers, Reinhold
|