Issues & Risks

[David F-H]

Is there a way to change the default categories (Category 1, 2, 3) for issues
and risks? I would like to have more categories with meaningful names.
Possibly may want to change priority and status definitions as well?.

 

[Jason Short]

Hi David,

If I have understood your question properly then this needs to be done via
the Sharepoint side of the installation. You will need Administrative Rights

Go the Project Workspace and click on the Site Actions Tab (Top right of
screen) and choose Site Settings. Under the Site Administration Column,
choose Site Libraries and Lists. Then click on Customise Issues (or Risks)
and from there you can click on Category and edit the values already in place.

 

[David F-H]

Thanks Jason, that's great. One further question then as I understand it -
this is done for each Project Workspace, but is there a way to set this up so
that new Project Workspaces pick up the modified Category descriptions when
they are created? Ie. Is there a way to set up a set of Category definitions
to be applied automatically for new Project Workspaces, or do you have to set
them up individually?

 

[Jason Short]

Hi David,

Yes I believe that this is possible but it would need to be tested first as
I have not done this before.

I belive that you would configure this by connecting to the Sharepoint
Central Administration site and configuring the settings there.

The location is the same i.e. Site Actions, Site Settings etc etc

 

[Gary L. Chefetz [MVP]]

David:

You can modify the base template that Project Server uses to create the
sites by creating a new one. Do not change the values in the Status field
for Risks or Issues.

--

Gary L. Chefetz, MVP
MSProjectExperts
For Project Server Consulting: http://www.msprojectexperts.com
For Project Server FAQS: http://www.projectserverexperts.com

 

[Jonathan Sofer]

There are several other fields that should not be changed either by name or
values like Due Date for example. A lot of out-of-box fields in the Issues
and Risks forms are hard coded into the reporting database and you will
start getting lots of queue errors on publishes if you change these fields.
Another option is to not use the out-of-box Issues and Risks lists and
create your own from scratch. You will lose some functionality though and
will not see them in the reporting database either.

Jonathan