"New from Template" and "Copy task", both having difficulties with dependencies.
carshow2
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?
Eberhard
how about defining your workflow once as an "external template" and
importing it, whenever needed?
I'd expect, that should work.
Eberhard
Neal
It does sound like in your example, however, that you can solve a lot
of your issues with just using the "complete subtasks in order"
checkbox. You really want to use that feature for all subtasks that
need to be done in sequential order. You only need to use
dependencies when the tasks aren't sequential...
On Apr 5, 1:12 pm, carshow2 <amichaelku...@gmail.com> 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 adependencyof the previous task (e.g. TaskB'sdependencyis
> 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 fromTemplate" and use Project1 as thetemplate, copy the
> whole thing, and then rename it Project2, all of the new tasks still
> show adependencyfrom Project1's tasks. For example, Project2's TaskB
> will show Project1's TaskA as adependency. What would be great is if
Andrey Tkachuk (MLO)
> if MLO would convert the dependencies of the newly copied
> tasks to the new tasks inside the new project I've created.
What version you are using? I have implemented this in 3.5.0.
Can you confirm that it works as expected in 3.5.0, 3.5.1?
Andrey.