Problem Report Information Page
A problem report documents a problem or a request for product enhancement.
The problem report information page is a collection point for information related to the problem report. The information page of a problem report is accessed by clicking the information icon 
.
.From the information page, you can perform actions on a problem report, as well as view the object attributes and any related information.
For an overview of information page functionality, see About Information Pages and Customizing Information Page Tabs.
Actions
Information pages contain a list of applicable actions in a menu in the upper left corner of the page. See Common Actions for a list of common actions available in Windchill. The availability of these actions depends on the status of the problem report, as well as your access to it. For more information about status indicators, see Object Status.
The View Summary Report action allows you to view a summary report of the specific problem report. For more information, see Viewing Change Summary Reports.
Tabs
The following tabs are viewable on the problem report information page. You can customize the tabs that appear on each object information page to display the information most useful to you. For more information, see Customizing Information Page Tabs
 | Administrators may have modified the tabs that are viewable to you. |
Tab | Description |
|---|---|
Details | The Details tab displays the attributes of the problem report, as well as related tables. See Object Attributes for a list of common attributes available in Windchill. The following attributes may be of particular interest for this object. • Category—The group under which the problem report is organized. Categories include things such as Cost Reduction, Design Issue, and Documentation Issue. • Change Admin I—The user serving as Change Administrator I for problem reports. This user is the initial reviewer of problem reports. • Need Date—The date by which the problem report must be satisfied. • Resolution Date—The date the problem report is resolved. • Issue Priority—The relative importance of the issue. The values for the priority include Low, Medium, or High. • Requester—The user name of the person submitting the problem report. In addition to the attributes of the problem report, the following related tables may appear on the Details tab: • Attachments • Annotations • Affected Objects—The local objects such as parts, documents, and other changeable and external objects. • Affected End Items (display of this table is controlled by a preference; the default is Yes) • Change Requests • Change Notices (display of this table is controlled by a preference; the default is No) • Associated Process Objects • Associated Reference Objects—The local and external associated reference objects. |
Process | The Process tab displays information about the processes that involve the problem report and includes the following tables: • Members—Displays the members of the team • Tasks for Change Process—Displays the tasks related to the problem report and any related changes • Routing/Process History, including the following: ◦ Routing/Process History ◦ Process Status ◦ Task History • Discussions—Displays the discussions related to the problem report and any related changes |
History | The History tab displays information about the history of the problem report and includes the following: • Timeline • Maturity History • Revision History—controlled by a preference; the default in No |
Related Topics