Change Requests

The change request component provides a defect tracking system that allows you to record defects in products, projects, or services and suggest possible enhancements. A change request is a request to change something within the scope of a project. For example, you might suggest a product enhancement or request a fix for an error or problem. To use the change request tracking system effectively, you need to understand the model on which it is based.

The change request component allows you to:

• Attach change requests to any folder. In the application, change requests can be attached to any project folder or shared among folders or other views in the same server configuration. You can also link a change request to any other item, such as a file. In many other defect tracking systems, a change request can be associated only with a project, even though it requires modification of a particular file.
• Save time when updating change requests. When you check in a file or group of files, you can indicate the change requests that are fixed by the files being checked in. This feature saves the time required to change the status of each change request separately.
• Make only appropriate status changes. When you create a change request, the status options are New, Open, Deferred or a resolution. The resolutions are Cannot Reproduce, As Designed, Fixed, Documented, and Is Duplicate. After resolution, a change request can only be verified or reopened. After verification, a change request can only be closed or reopened.
• Benefit from automatic changes based on the status of the change request. The application automatically changes the person responsible to coincide with the current status of the change request. When a change request is resolved, the responsibility for the change request automatically reverts to the person who entered the change request, who is usually the best person to verify its resolution. When a change request is reopened after being resolved, the responsibility is automatically set to the user who resolved it. If desired, you can override these automatic changes and make another person responsible.
• Base change requests on the build in which the change request is resolved. When a change request receives a Fixed or Documented status, the value of its Addressed In Build field becomes Next Build. When that build label is created, the application replaces Next Build with the name of the build label, letting testers know the build to use when verifying change requests.