i was also confused by this.
after playing around for a little while, it appears to me that...
1. folders can contain tasks and other folders
2. projects can contain tasks but NOT other projects.
3. tasks can contain other tasks
to add to the complexity/confusion, there are cases when the program will automagically convert a task to a project or a project to a task (e.g., using the indent/outdent commands), but there are also some cases where this will not work as you might expect.
anyone have an idea as to why projects can't nest hierarchically? it seems that only projects can have a "state" (active/on-hold/completed/dropped). so this seems to ensure that every implicitly inherits (at most) one single value state value, but i don't know if that has anything to do with why the limitation exists.
after playing around for a little while, it appears to me that...
1. folders can contain tasks and other folders
2. projects can contain tasks but NOT other projects.
3. tasks can contain other tasks
to add to the complexity/confusion, there are cases when the program will automagically convert a task to a project or a project to a task (e.g., using the indent/outdent commands), but there are also some cases where this will not work as you might expect.
anyone have an idea as to why projects can't nest hierarchically? it seems that only projects can have a "state" (active/on-hold/completed/dropped). so this seems to ensure that every implicitly inherits (at most) one single value state value, but i don't know if that has anything to do with why the limitation exists.