---
sourceDocument: Australia Security Management
sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/security-management

 Release :

    - australia

ft:locale :

    - en-US

ft:publication_title :

    - Australia Security Management

ft:clusterId :

    - security

bundleId :

    - security

workflow :

    - Technology


---

# Associate a remediation task to an existing change request

# Associate a remediation task to an existing change request {#ariaid-title1}

* Release version: Australia
* 
* Updated March 12, 2026
* 
* ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 4 minutes to read

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://servicenow-prod.fluidtopics.net/msi8kaFkGNjyRib_XBHEzQ "Assign the Vulnerability Response persona roles to groups or users with Setup Assistant."). For more information about managing granular roles, see [Manage persona and granular roles for Vulnerability Response](https://servicenow-prod.fluidtopics.net/WeKNf9YHNMJmJIA6yCsRvA "After you complete your initial assignment of persona roles using Setup Assistant, manage additional granular role assignments to users or groups from the User Administration module in your instance.").

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://servicenow-prod.fluidtopics.net/2YRZRrAyQGMEmEgDccN_pw "From a remediation task (VUL, AVUL, CVUL, or CRG), create a change request. Alternatively, add a remediation task to an existing change request.").

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://servicenow-prod.fluidtopics.net/2YRZRrAyQGMEmEgDccN_pw "From a remediation task (VUL, AVUL, CVUL, or CRG), create a change request. Alternatively, add a remediation task to an existing change request.").  
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.Figure 1. Workflow for associating a remediation task to an 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 (![Gear icon.]()) in the upper right. Move the CR count column from Available to Selected and click OK.{#vuln_change_mgmnt_associate_chng__CRCOUNTCOL}

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 AllVulnerability ResponseRemediation Tasks.
2. Locate the remediation task you are working with.
3. **Optional:** Navigate to AllVulnerability ResponseRemediation 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.
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.
8. Select an item from the displayed list, or, alternatively, click the filter (![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.
   {#vuln_change_mgmnt_associate_chng__simpletable_yr4_yhv_pjb__entry__2}

   | 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://servicenow-prod.fluidtopics.net/Cr79Ca3WRQu~t3SZ0tj0zg "There is a synchronized relationship between the State fields of remediation tasks (VULs) and the State fields of change requests (CHG) in the Vulnerability Response product. As a change request moves through its life cycle, it also moves the state of any related remediation tasks automatically."). |
   | 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. |
   [Table 1.]

   {#vuln_change_mgmnt_associate_chng__simpletable_yr4_yhv_pjb}
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.

*[\>]: and then