A repeated subset of Tasks

[Mark]

I have a set of tasks that happen over and over again through out the course
of a project. If one task changes, it should change for each instance where
that task is performed in the project. I'd like to create this task subset
once and then link it through out the project. The problem I run into, is
that it uses the dates and times associated with the subtasks each time I try
to link to it. I'd like it to utilyze the dates from the main project, not
the sub. Is there a way to do this?

 

[Mark]

After reading this, I decided it's maybe a bit confusing. Essentially, I have
a set of recurring tasks, but there is no real pattern to their reccurrence.
In other words, they might happen today, and again tomorrow, and again a week
later, but always the same subset of tasks. I'd like to find a way build this
subset as a self contained entity, so that if I chance a task within it, it
will affect everywhere it's used, but I'd like the reccurrence of the start
dates to be random, not patterned to always happen on certain days.

example:

Train Users in Atlanta on 2 December 5 days
Train Users in Detroit on 12 December 5 days (using the same tasks as on 2
dec)
Train Users in Seattle on 12 December 5 days (using the same tasks as on 2
dec)
Train Users in Omaha on 16 December 5 days (using the same tasks as on 2 dec)
Train Users in Chicago on 19 December 5 days (using the same tasks as on 2
dec)
etc.

I should have the ability to send my trainers to different cities, all
teaching the same subset of tasks, either on simultaneous days, or
overlapping, on ramdom days. Recurring, but a random recurrence. If I change
one of my training tasks, it should change for all.

Thanks again.

 

[Rod Gill]

There isn't unless you use VBA. Another approach though is to have the
duplicated set of tasks as a task list in Excel and only one task in Project
to represent the whole set. Simpler, quicker to schedule and the resources
still get a detailed task list.

 

[Steve House [Project MVP]]

I suggest they aren't the *same* tasks at all, only similar tasks. A task
is defined as an observable block of activity extending over time producing
a unique deliverable. While training workers to polish fids may involve
similar activities, the tasks for the Seattle workers produce a different
deliverable than do the tasks for the Atlanta workers and so are distinct
separate tasks. Think about it this way - is there any reason to believe
that if it takes 3 days to train 100 workers in Atlanta it will also take 3
days to train 100 workers in Seattle? I don't think so - there are many
factors that could enter into it so that it takes 3 days in Atlanta but 5
days in Seatlle to train exactly the same number of workers in exactly the
same set of skills. You can use copy-and-paste to cut down the typing when
first setting up your plan but from there not only is it difficult to
automate the process so that a change to one entry updates all of them, but
even if you could do it, it's very likely to produce a plan that is totally
bogus in the end result anyway. I know it's a PITA to update each set of
tasks by hand but hey!, that's why they pay PMs the big bucks <grin>.