PDA

View Full Version : Copied tasks dependencies...


liquor
09-04-05, 06:28 AM
Here's what im trying to do : we make different products and for each
products there are specific tasks to be done.

In dotProject, i created a project template with all our products this way:
1. created dynamic tasks
2. created multiple sub-tasks with depencies for each dynamic tasks

So I have for example:
Product A
sub-taskA-1
sub-taskA-2
sub-taskA-3
Product B
sub-taskB-1
...

where sub-taskA-1 must be completed before sub-taskA-2 and
sub-taskA-2 must be completed before sub-taskA-3

NOW: when i create a new project wich consist of 2 product A + 1 product C for example, i copy the parent tasks in my template project to my new
project so my project structure is almost all setup (only need to assign people, dates, etc).

The problem is: if i set the start date of the first sub-task of a product, I
expect all the following sub-tasks update automatically their start-finish (start date based on dependency is set ) but its not the case. It works in my original template but not the copied ones in my new project.

Any ideas?

liquor
13-04-05, 03:39 AM
bump

pedroa
13-04-05, 06:06 AM
bump?

When you copy the template project to your new project/product, this new product get's his tasks starting dates equal to the starting dates of the template project tasks, isn't it so?

You said "It works in my original template but not the copied ones in my new project." why? the dates are equal to the template, aren't they?

Isn't your sub-task really a task? and Product A a project? Didn't understand the "sub-" prefix.

What you were thinking is to set the start date of the first task and have dP recalculate the others?

I am just trying to figure out what is your problem here, not saying what's the solution, at least yet.

Pedro A.

liquor
13-04-05, 11:10 PM
Isn't your sub-task really a task? and Product A a project? Didn't understand the "sub-" prefix.
No. A project generally consist of multiple products. So i modelized them as dynamic tasks and the sub-tasks
are actually all the tasks under the dynamic task that need to be done to finish the product.

Project ABC
-Product A (dynamic task)
--sub-taskA-1 (task)
--sub-taskA-2 (sub-taskA-1 dependable)
...

Is it more clear now?
I create all product structures in a "template project" and when setup a real project, i copy the dynamic task(s) corresponding
to the product(s) we have to do for the project. now, i'd like to set the start date of the first task of each dynamic task in my
real project and dP set the following tasks start - end dates accordingly

Example:
Template:
-Product A
--sub-taskA-1 (start 01-01-2001 08:00/ end 01-01-2001 10:00)
--sub-taskA-2 (start 01-01-2001 10:00/ end 01-01-2001 11:00)

Real Project (copied the dynamic task including children into my real project)
Template:
-Product A
--sub-taskA-1 (start 04-13-2005 13:00/ end 04-13-2005 15:00) <--- i change this date but the next task keep the original date
--sub-taskA-2 (start 01-01-2001 10:00/ end 01-01-2001 11:00)

Its like if the "Set task start date based on dependency" gets broken after dynamic task being copied.

BTW bump is for "Bring Up My Post" ;)

liquor
14-04-05, 05:12 AM
I've done some tests heres what i found:

If a have a dynamic task and I copy it to another project (using the include children checkbox), the tasks dependencies between to copied children is not maintained. I i copy child tasks A > B > C I expected dP to set dependencies:
A' > B' > C'


Also : if i delete tasks , their task dependencies are kept in the DB. Is this normal?