Gap in risks

[Jacques Brink]

Hi,

I have a client that has to add 3 new risks to his project. But there are a
gap now between the risks. The previous risk that was recorder was 8 but
the 3 new risks started on 25. There is a gap now from 9 to 24 that has
risk ids but with no data. How can this be resolved and what can cause
this?

 

[Gary L. Chefetz [MVP]]

I think its quite possible to burn numbers without using them. You might
consider adding your own control number if this is bothersome.

--

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

 

[David Wells]

Hi Jaques,

I assume you are talking about Project Server 2003, as this "characteristic"
changes in 2007.

Each time you edit a risk, a new version of the risk is created (and
therefore a new risk ID number). This is how the system can list the risk
history when you view the each risk item. Risks 9-24 are versions of the
earlier risks. You can see all the consequtive risk ID's by removing the
filter Current = Yes in the default list views. This view shows all the
risks and all their versions.

So the reason you have gaps is because there have been a number of edits to
existing risks. The workaround is to create your own Risk ID and manually
enter it.

Project Server 2007 (or more specifically WSS 3.0) has a specific mechanism
for this - list versioning which you can set in the list settings. As a
result you don't have this problem.

Regards,

David
www.pcubed.com