Logging Change Requests
If the change request (CR) creator cannot find an existing CR that describes the issue, then the creator enters a new CR. The CR creator must enter all relevant details including the functional area for the problem, the environment (operating system, server type, and so on) where the problem occurs, and the precise steps for reproducing the problem.
The creator enters most of this information in the Change Request Description area of the Change Requests form.
To log a change request
- Navigate to the Quality screen, then the Change Request List view. 
- Create a new CR record, and complete the fields as appropriate. - Some fields are listed in the following table. - Field - Comments - Summary - Type a brief description of the CR. Enter a description that is concise enough so a reader can immediately understand the overall issue. - Type - Select the CR type. Accept the default value of Product Defect, or select another value to identify the CR as an enhancement request, a user interface issue, and so on. - Build - Select the product build in which the issue occurs. - Area - Select the functional product area for the CR. - Subarea - Select the functional product area subdivision related to the Area field that you select. When you select a value in this field, the Product Line, QA Owner, and Engineering Group fields are automatically populated. - Severity - Select an assessment of the seriousness of the issue. - Description/How to Reproduce - Type a detailed description of the issue. If the CR describes a product defect, then enter complete step-by-step directions for reproducing the issue. 
- Drill down on the Change Request number (#) field. 
- In the More Info form, complete the fields as appropriate. - Some fields are listed in the following table. - Field - Comments - Product Line - Displays the product line the CR affects. This field is automatically populated when you select a value in the Subarea field. - QA Owner - Select the quality assurance team owner of the CR. This field is automatically populated when you select a value in the Subarea field. - Special Tag - Select statuses or actions that other fields do not identify. You can use special tags for purposes such as reporting, tracking, querying, exporting, and localization. You can specify multiple tags. - Tag Summary - Displays all the tags that you select in the Special Tag field. - Comments - Type a comment describing actions for the CR and any additional information that other users might need to understand, track, or resolve the issue.