[curt.clifton]

Originally Posted by Shanana

Something I noticed a need for as I've set up my extensive project list... dependent actions. I love that a project can be set up to be either serial or parallel in terms of when a task becomes available. I find that, for most of my projects, I have a mid-sized list of actions. Most of these actions can be started right away but occasionally an action is dependent on one other task. I know that I could manage this with subprojects even when I have large projects with subprojects I'm running into a need for sub sub projects to handle this. For now, I'm just putting some of these one off dependent tasks in a waiting for context and then updating the context during a daily review when the task they were dependent on was completed.

This is one area that I struggle with also. I currently use combinations of parallel and sequential subprojects to get almost the precedence that I want. Currently my deepest project is 4 levels deep. But I also tend to punt future actions into catch-all subprojects to keep them out of the way. That works reasonably well, especially since the future actions often evolve as I get closer to them.

Do you have any thoughts on how dependent actions could be made less complicated than parallel and sequential subprojects? I haven't been able to figure out how dependent actions might be handled in the UI without adding something like Gantt charts as in OmniPlan.