Risks, Issues, Change Requests, and Action Items › Issues › How to Create Issues › Close Change Requests and Track as Issues

Close Change Requests and Track as Issues

You can quickly create a change request from an existing issue. Basic information from common fields is carried over to the new change request for easy setup. A link back to the originating change request is provided on the issue properties page for easy navigation between the records.

In addition, you can manually associate issues or change requests to each other. Association can help you understand the relationships between the issues and change requests, and provide better overall project management.

Click the ID in the Originating Change Request field to view the originating change request.

Follow these steps:

1. Open the change request page.

   The change request main page appears.

2. Complete the following field:

   Status

   Specifies the status of the change request.

   Values: Open, Work in Progress, Closed, or Resolved

   Default: Open

   Required: Yes

   Select "Closed".

3. Save the changes.

   The change request is closed.

4. Click Create Issue.

   The create page appears.

5. Complete the following fields in the General section:

   Issue Name

   Defines the short name for the issue. If you create an issue from a closed risk, the value for this field is from the Risk Name field on the risk properties page.

   Limit: 64 characters

   Required: Yes

   Issue ID

   Defines the identifier for the issue.

   Required: Yes

   Description

   Defines the short description for the issue. If you create an issue from a closed risk, the value for the field is derived from the Description field on the risk properties page.

   Required: No

   Category

   Defines the issue category to assign this issue. If you create an issue from a closed risk, the value for the field is derived from the Category field on the risk properties page.

   Values: Objectives, Sponsorship, Funding, Resource Availability, Interdependencies, Technical, Human Interface, Organizational Culture, Supportability, Implementation, and Flexibility

   Owner

   Defines the name of the resource who is managing the risk. This resource is responsible for verifying that the issue is managed and tracked appropriately through its lifecycle. If you create an issue from a closed risk, the value for this field is from Owner field on the risk properties page.

   Default: The resource currently logged in

   Required: Yes

   Status

   Specifies the status of the issue.

   Values: Open, Work in Progress, Closed, or Resolved

   Default: Open

   Required: Yes

   Creator

   Displays the name of the resource who created the issue.

   Default: The resource currently logged in

   Updated by

   Displays the name of the resource who last updated the issue.

   Default: The resource currently logged in

6. Complete the following fields in the Details section of the page:

   Target Resolution Date

   Defines the date for resolving the issue. The date requires to be the same or earlier than the impact date.

   Default: Current date

   Priority

   Defines the priority level for the issue.

   Values: Medium, Low, and High

   Default: Low

7. Complete the following field in the Attachments section:

   Document

   Specifies one or more attachments.

8. Complete the following fields in the Resolution section:

   Resolution

   Defines the final resolution of the issue after the matter is resolved.

   Required: No

9. Save the changes.

More information:

Create Issues