PWA Risks & Issues

[Rob]

At the bottom of the HOME page in PWA there are the 2 links to Risks and
Issues assigned to the user who has logged into the Home page. We are seeing
issues where these two options do not respond with the correct values.

It seems that only the Risks and Issues that are associated with projects
that the user is a Project Manager of show up on the Home page. So all other
risks and issues assigned to user on different projects are missing.

Has anyone seen this behavior before? and are there any suggestions or
solutions to this issue.

Any thoughts are much appreciated.
Thanks
Rob Cuscaden

 

[bnh1310]

Yes, I have seen the error and am searching for a solution. We recentl
added 100 + projects to our Database and have just started to see it
We have SP1 install for Project and Windows 2003 server SP1. I'v
tried re-synchronzing Sharepoint (both the site and admin accounts) n
change. I've tried re-saving and republishing the project. So fa
nothing works. It maybe isolated to a few users. Anyone hav
anything?

*At the bottom of the HOME page in PWA there are the 2 links to Risk
and
Issues assigned to the user who has logged into the Home page. W
are seeing
issues where these two options do not respond with the correc
values.

It seems that only the Risks and Issues that are associated wit
projects
that the user is a Project Manager of show up on the Home page. S
all other
risks and issues assigned to user on different projects are missing.

Has anyone seen this behavior before? and are there any suggestion
or
solutions to this issue.

Any thoughts are much appreciated.
Thanks
Rob Cuscaden

-
bnh131

 

[Gary L. Chefetz [MVP]]

This could be a permissions issue.

 

[Bnh1310]

Gary,
We have a large number of projects that we would like to assign
risks and issue to users that are not on the project team or assigned tasks
on the individual projects. For example: A Portfolio manager maybe assigned
issues and risks on several projects within the portfolio. We are seeing (or
rather not seeing) that unless the person is assigned as a team member of
that project, the home page never notifies the user of an existing risk or
issue. The manager and other resources show up and can be assigned an
issue/risk. But until they are added to the project team the item does not
show up on their home page. Can this be fixed? or is it by design?

 

[Gary L. Chefetz [MVP]]

In order for the home page to display the data, the user must have
permission to view Issues and Risks in the project in question. They get
that by either having an assignment in the plan, or by having the access
explicitly granted. In other words, you can assign an issue to a resource
who doesn't have permission to view it. Doesn't do much good does it? So,
like I said, it's a permissions issue. You can create this access using
Groups and Categories. Exactly what to do would depend on how you've
configured your security as well as other security requirements in play.

 

[Bnh1310]

Hi Gary,

Thanks for your response. However I maybe confused. First, all of
the users are a member of a security group I've created and specifically
granted "allow" the view issues, risks and documents check boxes for rights.
I've checked both the individual boxes under Permissions and the View risks,
issues and documents under the Catagories section for the group. All of the
projects are assigned in a catagory with those users specifically granted
access. The Catagory was created to assign specific views in PWA. What the
main issue is we have a series of team leads that maybe assigned risks or
issues in numerous projects. Most of these team leads are not assigned tasks
on the project plans. When a team member or project manager assign a risk or
issue to one of these team leads the item does not show up on the home page
in PWA. Do we have to assign them to a task on every project? They can
access documents for the project and view/open the projects just not be
alerted automatically of an issue or risk. Email notifications just when it's
assigned would not be enough. We are talking 100's of projects and 200 + users

Thanks!

 

[Gary L. Chefetz [MVP]]

Without seeing what you've done in your system, I can't begin to give you
specific instructions on what to do next. The best I can do is point you in
the right direction. If we step back for a second and think about this, an
issue, generally speaking, is a problem that someone has to do something
about. When you assign an issue to someone, it pretty much means that person
now has a task to do in order to resolve the issue. So, putting a linked
task in the Project Plan is how Project Server's designers thought this
would logically happen. You have that route available.

Otherwise the answer is the intersection between groups and categories.
Users must have global permission to see issues and risks and they must be
associated with a category that contains the project(s) where the issues and
risks occur and through that category have permission to view Issues Risks
and Documents for the projects contained therein.

Add tasks, or get the permissions straightened out.

 

[Bnh1310]

Hi Gary,

I understand the design behind the issues/risk. I have the
permission set the way you are referencing. Here are my observations. First
if Microsoft followed through on the assumption that if you had an issue or a
risk then you'd have to have a task on the project plan than only those on
the project team (build team from enterprise) should be the only users that
can be assigned an issue or risk. What about interproject dependencies. Maybe
an issue or risk of one project is that a linked or interdependent project
would not be completed on time? Sorry, Gary.
I think I've been working on this issue to hard. I certainly can tell them
to assign a task to someone on the project team. I just didn't think my
Sponsors and upper management should see all the tasks assigned to them just
in case someone assigns them a risk or issue.

 

[Arie]

Hi,

As a workaround you can do the following: in professional add all the
executives etc. that need to view risks/issues in PWA automatically updated
to the projectteam from the enterprise resource pool. No task assignment
nessesary, they only need to be part of the project team (because you would
like to see risks anyway this should not be a problem).

Maybe quick and dirty but it worked for us (about 100 projects and 300 users).