Master Plans in 2003

[projectserverdragon]

Why does the vendor not recommend the use of Master plans within project
Server 2003?

 

[Dale Howard [MVP]]

projectserverdragon --

If you publish a master project in Project Server 2003, the system
duplicates the task assignments of every resource assigned to tasks in each
of the subprojects. So, because of this, you should NEVER publish a master
project in Project Server 2003. On the other hand, you can safely SAVE a
master project, but make sure your Project Server administrator has disabled
the permission to publish a master project. The option is on the Server
Configuration page. Hope this helps.

 

[projectserverdragon]

I have found that I can publish a Master plan as long as I do not have the
sub plans opened within it.
If I publish a master plan with a subproject open it will actually duplicate
all of the tasks in the sub plan on the timesheet; however those duplications
will all be under the master plan project header.

Timesheet example:

Master.Sub.published
Task A
Task B
Sub.published
Task A
Task B


If I publish the master plan with all sub plans closed it will look correct:

Sub.Published
Task A
Task B


Is this exactly what you are referring to or are you speaking of something
different?

 

[Dale Howard [MVP]]

projectserverdragon --

Yes, that's what I'm describing. Given the potential problems that
publishing a master project can cause, do you really want to take the risk?
Hope this helps.