Thank you for your feedback.
Form temporarily unavailable. Please try again or contact to submit your comments.

Change request-project task relationship

Log in to subscribe to topics and get notified when content changes.

Change request-project task relationship

The relationship between project task and the project task link is governed by the same rules that apply to all parent-child tasks.

Start and end dates

The project task link inherits start and end dates from the change request. However, the Project application adjusts the dates when these situations occur:
  • If the project task and the change request have different planned start dates, the project task link uses the later of the two dates. For example, if the project task starts on October 1 but the change request starts on October 2, the project task link changes to October 2.
  • If the change request has an earlier start date, the Time constraint value for the project task link becomes Start ASAP when the link is created. The end date remains the same as the end date specified in the change request record.
  • If the change request starts and ends before the project start date, the project task link has a duration of zero (0) and therefore appears as a milestone that occurs when the project starts.
  • If a change request is scheduled to start during non-work time according to the project schedule, the planned start date of the project task link ignores the schedule and starts at the time specified by the change request. However, the duration of the project task link does take the schedule into consideration. Consider this example: the project uses the default schedule, which specifies that work hours are Monday to Friday from 8 A.M. to 5 P.M. with an hour break from noon to 1 P.M. A change request with a 13 hour duration starts at midnight. The project task link would start at midnight and continue through the start of the schedule at 8 A.M., stop at noon for one hour, and then continue from 1 P.M. until 2 P.M. The total duration would be 13 hours.

Project Task Duration

The duration of the change request determines the duration of the project task link, and that duration is rolled up to the parent project task just as all child task durations roll up to parent tasks. The Planned start date and Planned end date in the Change Request form's Schedule section are the fields that determine the duration. If there are no planned dates on the Change Request form, the default duration is one project day if the project has a schedule or 24 hours if the project has no schedule.

Multiple Linked Change Requests

f you link additional change requests to a project task, additional project task links are created, and they all become child tasks of the project task. The dates roll up to the parent task. For example, if a linked project task is planned to finish on October 30, but you link a new change request that is scheduled to finish on November 30, a new project task link is created. The parent task's planned end date extends to November 30 to cover the duration of both project task links.A change request can only be linked to one project task. It cannot be linked to multiple tasks in the same project or across multiple projects. A project task that has one or more child tasks cannot also have a project task link connecting it to a change request.

Project Task State

If the state of a change request changes to Pending, Open, or Work in Progress, the state of the project task link changes accordingly. If the state of the change request changes to any of the closed states, the state of the project task link changes to Closed Complete.

How Modifications Propagate Between Change Requests and Project Tasks

Modifications to a linked change request propagate to the project task link. However, the reverse is not true. You cannot modify the change request record from the Project application.

Modifications to the following fields propagate from the change request to the project task link:
  • Planned start date
  • Planned end date
  • State

These change request settings also roll up to the project task that is the parent of the project task link, and also up to the project record. Consider the following example: a project has not yet been started and all of its tasks are in the Pending state. If you changed the state of a linked change request record from Open to Work in Progress, the project task link, its parent task, and the project itself all change to Work in Progress.

When you start a project, tasks that have Start ASAP as the time constraint and have no other start dependencies start immediately. However, project tasks with linked change requests do not start automatically. The project manager must start the task manually by changing the State field to Work in Progress.

Modifications made in the Project application do not propagate to a linked change request record, so closing a project does not close a linked change. When you successfully implement a change and close the project it belongs to, you must go to the change request record and manually change the state to Closed.