--- title: Associate a remediation task to an existing change request description: As an IT remediation owner, avoid creating duplicate change requests \(CHG\) as you work to resolve your remediation tasks by associating a remediation task \(VUL\) to a change request that is already available in your instance. locale: en-US canonical_url: https://www.servicenow.com/docs/r/australia/security-management/vulnerability-response/vuln\_change\_mgmnt\_associate\_chng.html release: australia product: Vulnerability Response classification: vulnerability-response topic_type: task last_updated: "2026-03-12" reading_time_minutes: 5 breadcrumb: [Change Management tasks for Vulnerability Response, Vulnerability Response remediation overview, Vulnerability Response, Unified Security Exposure Management, Security Operations] --- # Associate a remediation task to an existing change request As an IT remediation owner, avoid creating duplicate change requests \(CHG\) as you work to resolve your remediation tasks by associating a remediation task \(VUL\) to a change request that is already available in your instance. ## Before you begin Persona and granular roles are available to help you manage what users and groups can see and do in the Vulnerability Response application. For an initial assignment of the persona roles in Setup Assistant, see [Assign the Vulnerability Response persona roles using Setup Assistant](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/security-management/vulnerability-response/vr-assign-personas_SA.md). For more information about managing granular roles, see [Manage persona and granular roles for Vulnerability Response](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/security-management/vulnerability-response/vr_manage_granular-roles.md). Role required: Any user with the itil role. The sn\_vul.remediation\_owner role is also assigned automatically to a user when the itil role is assigned. ## About this task For more information about associating a remediation task to an existing change request, see [Create a change request in the IT Remediation Workspace](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/security-management/it-remediation-workspace/vr-ws-CRs.md). The remediation task record is referred to as a VUL in the following sections. In previous versions of Vulnerability Response, remediation tasks were called, vulnerability groups \(VG\). In the following images, VG= remediation task, or a VUL record. For more information about associating a remediation task to an existing change request, see [Create a change request in the IT Remediation Workspace](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/security-management/it-remediation-workspace/vr-ws-CRs.md). As a remediation owner, you can associate remediation tasks that are assigned to you or your assignment group to existing change requests directly from the remediation task records. The following image illustrates the basic flow for associating a change request to an existing VUL \(VG\). The detailed steps for this flow follow the image. \[Omitted image "cr\_assoc\_flow.png"\] Alt text: Associate task to existing change request **Note:** You can associate an existing change request to a VUL in any state \(Open, Under Investigation, Awaiting Implementation, Closed, and Deferred\). When you associate a change request to an existing VUL, only the active VIs are added to the change request. Before you begin, to avoid creating duplicate change requests, you might prefer to view any existing change requests already associated with a VUL. To easily track the number of change requests that are related to a specific VUL, refer to the CR count column on the Remediation Tasks list. If not displayed, click the settings icon \(\[Omitted image "Banner\_GearIcon.png"\] Alt text: Gear icon.\) in the upper right. Move the CR count column from Available to Selected and click **OK**. To automatically populate the new column, for customers with existing data in this table, run the scheduled job: `Populate new CR Count Column`. ## Procedure 1. To associate a remediation task to an existing change request, navigate to **All** > **Vulnerability Response** > **Remediation Tasks**. 2. Locate the remediation task you are working with. 3. Navigate to **All** > **Vulnerability Response** > **Remediation Overview** to view the Remediation Overview dashboard and locate a VUL assigned to you or your assignment group. 4. In the Number column, click a VUL record to open it. The VUL record is displayed. 5. With the open record displayed, if not already displayed, scroll to the Change Requests related list and select it. Any change requests associated with the VUL are displayed along with the **Add** button. In the following figure, there are no change requests already associated with this VUL. \[Omitted image "cr\_associate\_add\_btn.png"\] Alt text: Add button on task record. 6. To associate the VUL with an existing CHG, click **Add**. The Add Existing Change Request to Remediation Task form is displayed. 7. In the form, click the search icon. A list view of existing change requests is displayed in a new window as shown in the following figure. \[Omitted image "cr\_associate\_CR\_list.png"\] Alt text: Change request list. 8. Select an item from the displayed list, or, alternatively, click the filter \(\[Omitted image "List\_FilterIcon.png"\] Alt text: Filter icon.\) and enter conditions to limit your search results. 9. For the Add CIs to CR check box, choose one to continue. **Note:** This check box is displayed only for existing change requests in the `New` state.
Option Description
Add CIs to CR check box selected Default is selected. If the check box is selected, any configuration items \(CI\) that belong to active vulnerable items in this remediation task are added to this change request.When selected, the state of the change request is synched to the VUL. For more information, see [State synchronization between change requests and remediation tasks](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/security-management/vulnerability-response/vuln_change_mgmnt_state_synch.md).
Add CIs to CR check box cleared Clear the check box if you do not want the CIs from the active vulnerable items from this remediation task added to the new change request.When disabled, the state of the change request is not synched to the VUL, and the VUL remains in its current state.
10. With the change request number you want displayed in the Search for Change Request field, click **Submit**. The VUL is displayed. At the top of the record, the blue confirmation message is displayed indicating that the change request you selected is successfully associated to the VUL. **Note:** For a VUL in the `Open` state with the Assignment group and Assigned to fields unassigned \(empty\), the current logged-on user is automatically assigned to the VUL after you click **Add**. In addition, the Add CIs to CR check box must be selected. At the top of the VUL, a blue confirmation message is displayed that indicates that the current user is assigned. ## What to do next Review the VUL record. In the Change Request column on the Change Requests related list, click link for the new CHG to view CR record. On the open CHG record, you can monitor the state of the change request. The affected configuration items \(CI\)s and the remediation tasks are displayed on the Affected CIs and remediation tasks related lists.