Using (1), (2), (3), etc. in Risks and Issues Category values?

[anovak]

Do most of you use numbers, like (1), (2), (3), to define Category
values for Risks and Issues to keep it "the same" as the out-of-the-
box values for Status? Just curious.

Thanks
Andy Novak
UNT

 

[alexb]

Andy,

I have used both with numbers and without for projects, based on the
clients maturity. I would suggest if you want to make it as easy as
possible to differentiate between the different risk and issues
categories, put the number in, it makes it much easier to see.

Alex.

 

[Vaso Vukovic]

... But keep in mind that if you change those values from lets say (1) Active
to 'Active' the WSS Sync process may not be able to correctly reflect the
number of issue/risks in your 'reminders' web part. If you are to do any sort
of business catalogue search/web parts on the farm level it would make sense
to have some business rules for lists categories (like should you use
brackets or not) to make it easier for developers to make queries against
site content..

for instance we gather all issues, risks, wss tasks etc in to one web part