The answer is "sort of."
You can modify the Assigned To field to accept multiple people, but in doing
so, you break the Risks/Issues reminder on the PWA main page. Of course
there's ways around that. I suppose you could somehow use a Page Viewer
webpart to point to a view filtering a specific list for a user.
If you want multiple Assigned To, and you want to aggregate that across multiple
sites, then you'll need to get clever in SharePoint, and either kludge something
up or work with a developer to assess a solution. Probably such a solution
would be based upon deploying Issues as centralized content types.
If they just look on the workspace for their own risks, here's how you modify
the assigned to field. The default views such as "View Issues Assigned to
Me" will still work.
1) List Settings
2) Click on "Assigned To"
3) Set it to accept multiple inputs
Disclaimer: changing some of the default list columns on a MOPS list may
end up throwing errors on Publish. I just tried it, and didn't get any errors,
but there's no guarantee.
If you want to move towards an aggregation solution, I would deploy Issues
as a content type, create a new column called Assignees (or something like
that), hide the old Assigned To field, then play around with Content Query
Webparts to try to aggregate.
A rough description of the first couple steps (sans aggregation) can be found
here:
http://blogs.catapultsystems.com/ep...-content-types-in-a-mossmops-environment.aspx
-A
