Issues, as the term is used in Project Server, are action items with a structured discussion about a specific topic. At all times an issue has an owner (such as a project manager or a team member) and a status (such as active or resolved). Use of issues is an excellent way to keep track of action items about projects, when the action items shouldn’t appear in the projects themselves. You can also think of issues as risks that evolved into actionable items and require tracking and mitigation.
As with risks and documents (described in the next section), you can associate issues with specific projects or tasks. You can also enable e-mail notification and alerts to keep track of issue status and see the status on all issues associated with a project.
In this section, we’ll see how to create a new issue and assign it to someone for resolution.
Steve Masters, a project manager at A. Datum Corporation, logs in to Project Server and navigates to the Issues Center.
Here Steve sees the list of the projects he manages (under My Projects) and other projects at A. Datum that he can view.
Steve wants to create a new issue for a task in the 100X DVD Drive project, so he clicks that project’s name.
The Issues page for the 100X DVD Drive project appears; currently it has no issues.
Steve clicks New Issue and, in the page that appears, enters the information he wants for the issue. Steve assigns the issue to Brad Sutton, a resource who has assignments in the 100X DVD Drive project.
Steve enters the issue information he wants Brad to act upon.
When he’s finished, Steve clicks Save and Close.
The new issue appears on the project’s Issues page, ready for Brad Sutton to resolve.
Associating documents with projects or tasks is an extremely useful capability afforded by the Project Server–WSS integration. Common types of documents you might want to link to projects or tasks include specifications, budgets, and various project management documents such as risk management plans.
There are two types of document libraries: project and public. For project document libraries, project managers set up the properties of the document libraries associated with their projects. Project managers can specify options such as the default templates to use for Office documents and access permissions to the documents. With public document libraries, all Project Server users have access unless the server administrator specifies otherwise. Both types of libraries support e-mail notification when a document has been changed. For documents in a project document library you’ll see visual indicators and links to those documents in the Project Center and Tasks Center.
In this section, we’ll see how to create a document library for a project and upload a document to the library.
Jo Brown, an executive at A. Datum Corporation, logs in to Project Server and navigates to the Documents Center.
Jo clicks the name of the 100X DVD Drive project, the project for which she wants to upload a document.
Jo sees that this project has not yet had a document library created for it, so she’ll do that next.
Jo clicks the Create Document Library link.
Project Server prompts Jo to enter information about this project’s document library and how she wants it to appear to Project Web Access users.
After recording the document library information she wants, Jo clicks Create.
Project server creates the new document library.
Jo already has the document she wants to add to this project’s document library, so she clicks Upload Document.
Jo browses to the document she wants and clicks Save and Close.
The uploaded document appears in the project’s document library.