Project Workspace List Customisations

[David F-H]

We are running Project Server 2007 / SQL Server 2005. I have seen advice in
the forum regarding not changing the Status field list values in Project
Workspaces as there are dependencies from Project Server on the home page,
etc. Are there any other fields within Issues or Risks in Project Workspaces
that should not be modified (eg. Priority, etc) because of links with Project
Server pages, or even Portfolio Server? We are planning to change the drop
down list for the Category field to have different values, and save as part
of a workspace template that will be assigned as our Default Project
Workspace template.

 

[Paul Conroy]

David,

I wouldn't change ANY of the default fields, instead hide those you don't
wish to use from the list views, and create new custom fields using
alternative names.

Paul

 

[David F-H]

Hello Paul,
the trouble with project workspace custom fields is that they aren't brought
across to the reporting database, and so we can't get a consolidated report
across all project workspaces - that's why we are looking at changing the
default lists, so just wanted to make sure we're not changing anything that
is used by Project Server (like Status field is).