Additional Issue Categories

[Brian Lukanic]

I understand the problem when one starts messing with the default
columns/choices in WSS workspaces. However.....

I'd like to add a 4th option in the issues category. I'd like to know if
there's any way to get this to show up in the /pwa/pws/issueriskcenter.aspx
view:
(1) Active
(2) Postponed
(3) Closed
(4) Escalated

I've done some tests and can at least confirm that the addition of an
additional option will at least not break functionality or the counts on the
issues/risks page. But ultimately, I'd like that issues/risks page to SHOW
the 4th option. I've poked around the XML a bit but am afraid to try to
insert the 4th column. Has anybody had any luck with that?

If I cannot get escalated issues to show on that main dashboard then I will
write a custom list rollup web part that will query all issues lists for that
critera. Won't be as elegant as the native dashboard but I can probably get
it to work.

Similarly - that /pwa/pws/issueriskcenter.aspx page seems to have the
potential to get very deep with rows after a few months of project
management. Let's say a resource has been on over 100 projects in the course
of a year and has only 12 projects with open issues for them. Looks like the
still get a row for each old project, with all counts at zero. Is there any
way to remove from view any projects that have no active or postponed issues
for the user? The Closed count almost is meaningless and I'd prefer to not
take up a row for it. I'm worried that the only answer would be to delete the
original issue from the workspace, which would be bad for reasons of keeping
historical information.

I like the default issues/risks dashboard but the ability to customize seems
frustratingly limited.

 

[Marc Soester [MVP]]

Hi Brian,
that is a request often asked and the answer to this is unfortunalty no. You
can easily extend the category list and can report against it, but in order
to increase the functionality of the risk/issue page, you will need to do
custom development.

A nice work around is to create a report that users can see on the homepage.
Hope this helps