Issues and Risks counts on homepage

E

Earl Lewis

If anyone has ever wondered why their issues and risks counts weren't showing up or were showing incorrect counts I've discovered one reason this may happen. As you might have guessed this happened to me.

Being the accomodating project manager that I am I thought I was doing my users a favor by making the issues/risks lists appear a little neater so I went ahead and changed the status codes by removing the leading numbers and parentheses that M$ puts in there by default. Well, you guessed it, they look for those specific values, parentheses, numbers and all - at least when it comes to determining "active" issues and risks. Ergo, my "active issues" messages on the homepage were entirely inaccurate.

In my opinion this is a bug that M$ should fix by either:

1) provide a mechanism that allows the label names to change while the underlying status values remain constant, thus it wouldn't break if I wanted to call the status "open" instead of "active" or remove the number and parentheses or whatever OR

2) remove the ability to customize the issues/risks lists or those specific fields if changing them will break the PWA homepage display - which is NOT a viable solution in my opinion. Especially considering that this would be a simple table addition or modification and then pointing the appropriate views and stored procedures at the new "label lookup" table.

Just an FYI for anyone out there that may be experiencing this problem.

Earl
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Top