Summary Tasks and Grouping in Project View

[David Schmitt]

I have been unsuccessful in creating a Project view in Project Server that is
similar to the "Priority Keeping Outline Structure" grouping in Project
Professional. My goal is to group by one of the fields in the Project view,
but I want to keep the Outline Structure (the organization of the tasks
within the various summary tasks).

In Project Pro this is done by grouping first by Outline Number, then by the
field you want to group by. An example is the "Priority Keeping Outline
Structure" grouping that comes with Project Pro. However, if I group by
Outline Number in a Project Server view, there are two differences that make
the solution unusable:
1) The entire outline number of a task is used for grouping, rather than the
outline number of the summary tasks. Since each task has a unique outline
number, each task is in its own group. This renders the secondary grouping
useless.
2) The name of the task is not shown in the grouping so even if the first
problem didn't exist, I wouldn't know which grouping to expand.

For example, my Project Pro grouping is "2 Software | 2.1 Iteration 1 |
Resource1, Resource2, Resource3", my Project Server grouping is "2 | 2.1 |
2.1.1, 2.1.2, 2.1.3...".

Does anyone know a way I can replicate the functionality of the "Priority
Keeping Outline View" within Project Server? I want to use this view as a
means whereby everybody can view team's progress within an iteration.

Thanks for your help,

David Schmitt
Medical Simulation Corporation

 

[Mike]

David

You need to create a task enterprise outline code and assign to each
task. The description against the outline code will be displayed in
the Project View. Clearly you have to manually assign the correct code
to each task. Also code is applicable to all projects.

regards

Mike

 

[David Schmitt]

Mike -

Thank you for your response, but this seems like an extremely cumbersome
solution. It would require me to replicate my entire project structure of
summary tasks as a task-level outline code, then assign them to each task.
And if I move a task from one summary section to the next (which happens
frequently as tasks are moved from one iteration to the next), I would have
to make sure to adjust that field. Finally, the structure of summary tasks
is not identical between projects, so this would have to be done for each
project.

The Project Pro view comes without manual effort. I'm hoping to find the
same capability in PWA.