I’m having trouble understand the implementation of subprojects in OF2. In OF1 if I dragged some actions into another action, the parent action would become a subproject. It would lose it’s completed/context fields since it’s no longer an action, etc, making it clearly become a container and not an action. But in OF2 it retains those so it appears as being an action with a context also containing other actions with their own contexts. This is really confusing, how can the parent action have one context and the children actions have their own contexts? How can a parent action have one due/defer date and children another? I don’t understand what exactly this “container action” is supposed to be. In OF2 parent actions/subprojects have become this pseudo half-action-half-subproject which I’m not sure what to do with.
This becomes even more confusing in Contexts. Both ‘subprojects’ as well as top level projects show up in Contexts as actions that you can check off etc. This makes no sense to me in the context of GTD or in general, you don’t check off projects, you check off actions. I have a hard time telling if I am checking off an action or a top level project and this is dangerous because I could accidentally check off a ton of actions. There should be some way to hide Projects and Subprojects in context view.
Finally, why don’t subprojects show up in the sidebar just like subcontexts do? It would make subprojects more useful.