Prioritizing and Assigning Change Requests
If the product manager determines that the issue in a change request (CR) is new and an owner must resolve it, then the manager assigns a priority, a target release, and an owner to the CR. The product manager usually assigns the CR to the engineering manager who is in charge of the product area relating to the issue.
The product manager enters priority and assignment information in the Resolution section of the Change Requests form.
To prioritize and assign a change request
Navigate to the Quality screen, then the Change Request List view.
Select the CR record, and change the fields as appropriate.
Some fields are described in the following table.
Field Comments Owner
Select the engineering manager who manages resolving the reported issue in the CR.
Priority
Select the urgency to resolve the issue compared to other issues at hand. The value in this field can be different from the value in the Severity field.
Targeted Version
Select the release in which to fix the CR issue.
Drill down on the Change Request number (#) field.
In the Comments field of the More Info form, add a comment summarizing the reasons for your prioritization and assignment of this CR.
Complete the other fields as appropriate.
Some fields are described in the following table.
Field Comments Engineering Group
Select the group that delivers the resolution. 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.