Quote:
|
Originally Posted by Athanasius
I'm curious as to why you would use projects as tasks.
|
Well, according to David Allen, a task that has more than one step is a project - So essentially, a task with a subtask is a project.
Creating subtasks (sub-projects) is implemented very nicely. However, my question is why are the main projects not like sub-projects?
E.g.: I have a single task - lets say "Call John and catch up on old times". It clearly belongs into my @calls context, but is a single task. I might have it in a project group called "Social stuff" but it does not belong into a project - a sub-task of a task with many steps.
Instead of classifying it as a sub-task, I would like to classify it as a main task - a "project" (as in "project level in the sidebar hierarchy". I can then put the "project" into a group called single tasks if I want.