Assigning Issues in PWA

[joeM]

I would like to assign an issue to one (or more) of the 100+ resources whose
Project Server accounts are active. For reasons unknown to me, the "Assigned
to" pull-down list contains a very abbrieviated list of about 20 active
resources. What little documentation I have found on this feature leads me
to believe the list should be populated by members of the project team who
have permission to edit issues. That doesn't prove out as my project
contains only one team member. I have the same question regarding the "Issue
Owner" pull-down list. How do these two fields works? Thx!

Joe Messina
MedPlus, Inc

 

[ron]

after much research, it turns out that only enterprise
resources who are assigned to the team AND assigned to
tasks in the project plan appear in the list.

Also, you should probably be aware that the task id
referenced by the link is the Unique ID, and the display
names are the Active Directory names, not those in Project
Server.

hope this helps.

 

[joeM]

Thanks Gary. What I (think I) learned since my initial post (and from Ron's
reply) is that Project Server passes those users that are assigned to each
project -- plus those users who have heightened permissions (Project Lead,
Project Manager, Resource Manager, Portfolio Mgr, Executive, Admin) -- over
to STS when the subweb is created. In my case that occurs when the project
is first published. Assuming their accounts are active, all of those users
will show up in the pull-down list within the Issue. If other "mere mortals"
(Team Members) are assigned to the project after the initial sync between
the Project Server and STS Server, you have to make sure the assignments are
republished and then manually synchronize the servers using the Admin>Manage
STS>Manage Subwebs>Sync Users option. In order to satisfy the need of
assigning an issue to any user, I have to make sure that everyone that is
conceivably associated with a project is assigned to a task within those
projects. Unless somebody has a better idea, the only workaround I can think
of is to assign the remaining 60-something folks in the organization (the
ones that don't belong to the elite roles) to a dummy task in the project.
That way everybody gets invited to the party. I have no idea what impact
that has on performance or DB size.

I'm resistant to following your recommendation as I feel that making more of
the STS services (like Documents) visible to the public will muddy the water
here. We are still in the process of deploying SPS and I have no doubt the
introduction of some attractive STS services (General Discussion, Lists,
Issues, etc.) that don't exist in SPS will generate a series of requests for
more bells and whistles -- before we nail down basic document management
practices. Right or wrong, I'm taking the "less is better" approach for now.
Make no mistake though... I truely appreciate your many posts to this
newsgroup! It's a tremendous help to folks like me who are flailing out
here.

Joe