Thanks Lisa, I actually thought of that. but it's just too much trouble. I've noticed that there are a chunk of processes that stick together and need to be done in succession. The ability to branch would be really useful.
Also, because of the nature of the projects, dependencies are extremely important. One of the worst setbacks I've found is the fact that dependencies cannot be exported in MLO or set up to be relative to a task. Which means that I cannot create a "master task list" full of dependencies and re-use it without having to set up the dependencies all over again. I absolutely love the way MLO handles the tasks in the To Do list. I would love to have that tool to guide me through my daily tasks at work, but I sincerely don't have the time to plan projects from the ground up every time around. Rgds, Gaston On Nov 23, 5:12 pm, Lisa Stroyan <[email protected]> wrote: > >For example, a task that can be answered Yes or No and that would > >trigger a different set of tasks to be activated or deactivated. > > It would be a bit kludgy but you could have two tasks, the "Yes" task > and the "No" task (which I believe could be hidden from the Todo > view), and then a different set of children tasks that are dependent > on each of those, so they only show up if Yes or No is completed (checked). > > Of course later you would want to delete all of the other branch, > which would be a pain. > > Lisa > > ---------- > Lisa Stroyan, mailto:[email protected] -- You received this message because you are subscribed to the Google Groups "MyLifeOrganized" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/mylifeorganized?hl=en.
