Problem Reports and Variances in Projects
The front end of the change management process can be extended to the collaborating members who participate in the project context. The problem reports and variances that are managed in the project context are reviewed and prioritized accordingly, along with other problem reports and variances that are managed in the product, quality, or library contexts. For more information on the change management process, see About Change Management.
In project contexts, you can create and edit problem reports and variances against a shared object. Project problem reports and variances are intended to remain in the project context and do not exist in the product context. In addition, problem reports and variances can be shared to the project context when visibility is needed for the collaborating members.
 |
In order to create and edit problem reports in a project, your administrator must set the Problem Reports in Projects preference to Yes and you must have the proper access control permissions. In order to create and edit variances in a project, your administrator must set the Variances in Projects preference to Yes and you must have the proper access control permissions. See Administration of Problem Reports and Variances in Projects for more information.
|
|
|
Project contexts do not support revisions; therefore, problem reports and variances in projects are not revisable.
|
|
|
You cannot route problem reports and variances.
|
For information on creating problem reports and variances in project context, see Creating a Problem Report in a Project and Creating a Variance in a Project.