Risks, Issues, Change Requests, and Action Items › Change Requests › How to Create Change Requests › Create Change Requests from Issues

Create Change Requests from Issues

Create a change request when a change to the project plan is required. You can capture basic information about the circumstances, impact, reasons, and time frames for changes to the project scope.

Follow these steps:

1. Open the project and click Risk/Issues/Changes.

   The risks page appears.

2. Open the Risks/Issues/Changes menu and click Issues.

   The issues page appears.

3. Click the name of the issue.

   The issue main page appears.

4. Click Create Change Request.

   The create page appears.

5. Complete the following fields in the General section of the page:

   Change Request Name

   Defines the short name for the request.

   Limits: 64 characters

   Required: Yes

   Change Request ID

   Defines the unique identifier assigned to the request for tracking. Once the risk is saved, the request ID cannot be changed.

   Description

   Defines the short description of the request.

   Required: No

   Category

   Defines the category to assign the request to.

   Values: Flexibility, Funding, Human Interface, Implementation, Interdependencies, Objectives, Organizational Culture, Resource Availability, Schedule Risk, Sponsorship, Success Risk, Supportability, or Technical.

   Owner

   Specifies the name of the resource managing the request. The resource is responsible for verifying that the request is managed and tracked appropriately through its lifecycle.

   Default: The resource currently logged in

   Required: Yes

   Status

   Specifies the status of the change request.

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

   Default: Open

   Required: Yes

   Creator

   Displays the name of the resource who created the request.

   Default: The resource currently logged in

   Date Created

   Displays the date of creating the request.

   Updated By

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

   Default: The resource currently logged in

   Date Last Updated

   Displays the date of last updating the request.

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

   Reasons

   Enter the reason for the requested change.

   Priority

   Defines the priority level for the change request.

   Values: Medium, Low, and High

   Default: Low

   Required: Yes

   Expected Close Date

   Defines the date by which you expect to close the request.

   Next Review Date

   Defines the date by which the next review for the request is likely to occur.

   Date Closed

   Enter a close date for the request.

7. Complete the following fields in the Effect section of the page:

   Impact on Baseline

   Describe how the changes in the request can affect the project baseline.

   Impact on Other Projects

   Describe how the request can affect other projects.

   Benefits

   Describe how the change can benefit the project.

   Change in Cost

   Defines the amount by which the request can change the budget cost of the project. The budget cost is a field defined on the budget properties page.

   Change in Schedule

   Defines the number of days by which the request can delay or hasten the overall project schedule.

   Change in Resources

   Defines a number that reflects the request for an increase or decrease in the number of resources needed for the project.

8. Complete the following fields in the Assessment section of the page:

   Assessor

   Defines the resource responsible for assessing the request.

   Date Assessed

   Defines the date for assessing the request.

   Approved By

   Defines the resource responsible for approving the request.

   Date Approved

   Defines the date for approving the request.

9. Save the changes.

More information:

Create Change Requests

Edit Change Requests