Dear carshow2, how about defining your workflow once as an "external template" and importing it, whenever needed?
I'd expect, that should work. Eberhard On 5 Apr., 20:12, carshow2 <[email protected]> wrote: > I use MLO frequently for projects that I will have to do certain > things in order, and these certain things remain the same for each > project. For example, say I have Project1, and I have TaskA though > TaskF (so TaskA, TaskB,etc.). Now, each task starting with TaskB will > have a dependency of the previous task (e.g. TaskB's dependency is > TaskA), so that at all times there is only one "active" task. > > As I said, I have several projects, all of which will have an > identical structure (I do consumer bankruptcies, an intensively > process-driven area of law, and I want to make sure I get everything > done, and in order), so it would very handy if I could simply copy a > "template" set of tasks. Unfortunately, if I copy Project1, or if I > select "New from Template" and use Project1 as the template, copy the > whole thing, and then rename it Project2, all of the new tasks still > show a dependency from Project1's tasks. For example, Project2's TaskB > will show Project1's TaskA as a dependency. What would be great is if > someone could let me know how, when I copy a whole set of tasks, all > of whose dependencies are entirely contained with the tasks I've > copied, if MLO would convert the dependencies of the newly copied > tasks to the new tasks inside the new project I've created. > > Any suggestions? -- 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.
