Summary task roll-down?

J

Jørgen

Hi, the awkward subject has it's explanation.

I'm trying to introduce a Change request field in a table.
The Change request field is valid for summary tasks,
meaning that all tasks within are implicitly contributions
to the same change request (therefore the roll-down). I
would like this to be a mandatory field so that we know if
a group of tasks are related to CR's or implementing a new
feature.

The structure is as follows
Phase
- Activity
- Tasks

I would like to implement the CR field in the Phase level,
making it valid for both activity summary level and it's
associated tasks. There might be several Phase summary
tasks within a project plan, which in turn can relate to
different CR's. It just causes overhead to repeat the same
CR number to all phase activities and tasks.

Anyone have a good solution to this?

Brgds,

Jørgen
 
J

Jon Smith

Yes, create 3 custom fields: Number (for the CR #), Cost
(for the CR $), Number (for the CR hours). Insert those
in your Task Sheet template as columns with the rollups.
If a CR spreads over several phases, thats no problem.

Then create a custom grouping by CR Number. This will
show all of the tasks under the CR, regardless of phase.

Hope this helps
r/Jon
 
R

Rod Gill

Hi,

Summary tasks are just that, they summarise their sub-tasks. And field
edited in the Summary task, does not ever, therefore, roll down. To get this
effect you need to write a VBA macro.

To duplicate numbers manually, select the cell in the Summary tasks then
click and drag to select the same field for the sub-tasks then Ctrl+D to
fill down.

Alternatively there should be a selection dot in the bottom right corner of
the selected cell. drag it down over the sub-tasks and Project should fill
down automatically.

--
Rod Gill
Project MVP
For Microsoft Project companion projects, best practices and Project VBA
development services
visit www.projectlearning.com/
Hi, the awkward subject has it's explanation.

I'm trying to introduce a Change request field in a table.
The Change request field is valid for summary tasks,
meaning that all tasks within are implicitly contributions
to the same change request (therefore the roll-down). I
would like this to be a mandatory field so that we know if
a group of tasks are related to CR's or implementing a new
feature.

The structure is as follows
Phase
- Activity
- Tasks

I would like to implement the CR field in the Phase level,
making it valid for both activity summary level and it's
associated tasks. There might be several Phase summary
tasks within a project plan, which in turn can relate to
different CR's. It just causes overhead to repeat the same
CR number to all phase activities and tasks.

Anyone have a good solution to this?

Brgds,

Jørgen
 
J

Jørgen

Jon,

thanks for the answer, but I think the answer is a bit
more complex. I forgot to explain the context in which
this CR feature will be used. I am currently implementing
the macro as shown in Techrepublic to import task data to
the OLAP Cube. Doing so, I'm only interested in the
summary level information of a phase and it's associated
activities and tasks.

I'm having a bit of a problem with copying the enterprise
task information into the enterprise assignment
information since I don't want to assign resources to
summary tasks.

Now, as you can see the problem has grown to be more
complex.

But thanks for replying anyhow.

/j
 
Top