--- sourceDocument: Australia Strategic Portfolio Management sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/pt-BR/it-business-management Release : - australia ft:locale : - pt-BR ft:publication_title : - Australia Strategic Portfolio Management ft:clusterId : - itbm bundleId : - itbm workflow : - Technology --- # Change requests and project tasks # Change requests and project tasks {#ariaid-title1} * Versão de lançamento: Australia * * Atualizado 12 de mar. de 2026 * * ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 5 min. de leitura Large-scale changes approved by your change approval board (CAB) require new or existing projects to be implemented. To bridge the gap between change management and project management, the instance allows you to link one or more change requests to a project task. You can link an existing change request to a project task or create a new change request directly from a project task. When you link a project task to a change request record, a new project task link record is created. It provides the actual link between the project task record and the change request record. The project task link copies all attributes of the change request record. It then becomes a child task of the project task that you linked to the change request. The rules that govern the relationship between the project task and the project task link are the same as the rules for all parent and child tasks. Figura 1. Project tasks linked to change requests Nota: A project task cannot have both task link records and child project tasks. When a project task is linked to a change request, you cannot also create child tasks for that project task. Likewise, when a project task has child tasks, you cannot link the parent project task to a change record. The project task link record is read only. You can view the project task links from a related list on the Project Task form. Figura 2. Project Tasks Links related list You can also link multiple change requests to a single project task. In this case, a project task link record is created for each link and all the project task link records become child tasks of the project task. Figura 3. Project tasks links ## Change request project task relationship {#c_ChangeRequestsAndProjectTasks__section_m3k_2wh_yfc} The rules that apply to all parent-child tasks also govern the relationship between project task and the project task link. The project task link inherits start and end dates from the change request. However, the Project Management application adjusts the dates when these situations occur: Start and end dates: * 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). It also 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. It also starts at the time specified by the change request. However, the duration of the project task link does take the schedule into consideration. For example: the project uses the default schedule, which specifies that work hours are Monday to Friday from 08:00 to 17:00 with an hour break from noon to 13:00. A change request with a 13-hour duration starts at midnight. The project task link starts at midnight and continues through the start of the schedule at 08:00. It stops at noon for one hour, and continues from 13:00 until 14:00. The total duration would be 13 hours. {#c_ChangeRequestsAndProjectTasks__ul_sml_bly_dq} ## Project Task Duration {#c_ChangeRequestsAndProjectTasks__section_n3k_2wh_yfc} The duration of the change request determines the duration of the project task link. 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 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. The project has a schedule or 24 hours when the project has no schedule. ## Multiple Linked Change Requests {#c_ChangeRequestsAndProjectTasks__section_o3k_2wh_yfc} If you link additional change requests to a project task, additional project task links are created. 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. You link a new change request scheduled to finish on November 30, a new project task link is created. The parent task 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 {#c_ChangeRequestsAndProjectTasks__section_p3k_2wh_yfc} 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 {#c_ChangeRequestsAndProjectTasks__section_q3k_2wh_yfc} 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 Management application. Modifications to the following fields propagate from the change request to the project task link: * Planned start date * Planned end date * State {#c_ChangeRequestsAndProjectTasks__ul_ipk_qly_dq} 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 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 Management 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. **Conceitos relacionados** * [Parent-child rollup task calculations](https://servicenow-prod.fluidtopics.net/QLtCHncIxoq2XWyqFjFQtA "Date changes, stage changes, and value calculations roll up from child tasks to parent tasks.") * [Schedule conflicts between project tasks](https://servicenow-prod.fluidtopics.net/24adzqUmwt~TJV75txYwvw "Scheduling conflict helps you to identify project tasks that are not honoring dependencies. A scheduling conflict occurs when one project task prevents other task from starting on the specified date because of dependencies or constraint types.") * [Project task checklists](https://servicenow-prod.fluidtopics.net/KGvRjnLedJ8AgZL803vc3g "A project task checklist gives you the ability to track activities that must be completed on a task.") * [Task resources](https://servicenow-prod.fluidtopics.net/vr6xliimeQDEFPp7XHWU4g "Resources are the individuals or groups assigned to perform tasks and subtasks in Project Management.") * [Project and project task states](https://servicenow-prod.fluidtopics.net/oTapSkYalOsDpLqqN~7D0A "In the base system, the states in project and project task inherit the states in Task table.") * [Composite Fields](https://servicenow-prod.fluidtopics.net/_Ekygqsh1N58ko8wLQv7PQ "A composite field combines information from two fields in a table to form a single field.") * [Cost plan breakdown](https://servicenow-prod.fluidtopics.net/HFCUvdtn77ZK5cI4HNR0tA#cost-plan-breakdown "A cost plan breakdown captures the estimated cost and actual cost for every fiscal period. Cost plan, project, demand, program, and portfolio are the breakdowns types that are available.") * [Actual project costs](https://servicenow-prod.fluidtopics.net/D6knKsFEjan~h1w9WcbgZA "Actual project costs come after you create expense lines for cost plans or after human resources use time cards to create expense lines.") * [Types of external dependencies](https://servicenow-prod.fluidtopics.net/bBkp5cwu2bPkIcsndlOAew "The Project management application supports two types of external dependencies - hard and soft.") * [Project and portfolio funding](https://servicenow-prod.fluidtopics.net/5SMD6RCiVZPTYJ8T3T6nRQ "Specify the amount of money that projects and portfolios are allowed to have.") **Tarefas relacionadas** * [Project tasks](https://servicenow-prod.fluidtopics.net/xtVpKa1FDFRp3DJZHCbQSA "Create project tasks in several ways, even from other applications in the instance.") * [Link change requests to a project task](https://servicenow-prod.fluidtopics.net/iGzHYuvagRlCywjoah9iKg "Link change requests to tasks on the Project Task form. You can link change requests only to project tasks that have no child tasks.")