---
sourceDocument: Australia IT Service Management
sourceDocumentLink: https://www.servicenow.com/docs/r/australia/it-service-management

 Release :

    - australia

ft:locale :

    - en-US

ft:publication_title :

    - Australia IT Service Management

ft:clusterId :

    - itsm

bundleId :

    - itsm

workflow :

    - Technology


---

# Import based evidence collection

# Import based evidence collection {#ariaid-title1}

Release version: Australia  
Updated March 12, 2026  
![](https://www.servicenow.com/docs/portal-asset/ico-clock) 3 minutes to read
Summarize  
![AI sparkle icon](https://servicenow.com/docs/portal-asset/ai-sparkle-icon) Summarized using AI  
This content was generated using new OpenAI-powered functionality. Results are provided on an as is basis and are not guaranteed to be accurate or complete.  

## Summary of Import based evidence collection

Import based evidence collection is a feature in ServiceNow's DevOps Change management that reduces instance overhead by skipping step-level pipeline processing.
It accelerates change management and evidence collection for orchestration tools including GitHub Actions, Azure DevOps (ADO), Jenkins, and GitLab.
Instead of using webhook notifications, all relevant pipeline evidence is attached to the change request through an import request mechanism.
Show full answer Show less  
This feature can be enabled via the **Import based evidence collection for orchestration capability** toggle on the DevOps Change Velocity properties page. Enabling it modifies event processing to ignore step-level events and process evidence primarily at pipeline completion, reducing processing load on the instance.

## Enablement and Usage

* **Toggle Setting:** Turning on the toggle skips step-level event processing; turning it off reverts to standard full processing.
* **Important:** Ensure no active pipelines are running when switching this toggle to avoid hanging pipelines or incomplete data collection.
* **Manual Intervention:** If a change request exists during toggle switching, it must be manually canceled to ensure evidence attaches correctly.
* **Process Flow:** When a pipeline change step triggers, an import request collects evidence and attaches it to the change request. This process repeats at pipeline completion to ensure all data is captured.

## Tool-Specific Behavior

* **Azure DevOps (ADO):** For build pipelines, evidence collection happens only at pipeline completion when enabled; release pipelines still process step-level events.
* **GitHub Actions:** Collection occurs at workflow completion only. If using Deployment Gates, configure the GitHub app accordingly.
* **Jenkins:** Evidence collection is based on pipeline completion only. Requires installing the latest ServiceNow DevOps Plugin from the Jenkins Marketplace.
* **GitLab:** Collection occurs based on pipeline events webhook only; manual jobs (with "when: manual") are not supported.

## Key Features and Limitations

* Supports all pipeline styles including reruns, parallel, and sequential for GitHub Actions, Jenkins, and ADO.
* Supports all existing evidence collection types for GitHub Actions, ADO, GitLab, and Jenkins when enabled.
* Does not support environment-based changes for GitHub Actions or manual jobs for GitLab.
* Jenkins Freestyle pipelines are not supported.
* Historical import, polling features, and troubleshooting frameworks function the same regardless of toggle state.
* Restarting import requests is supported.
* By default, this capability is disabled upon upgrading.

## Practical Benefits for ServiceNow Customers

Enabling import based evidence collection improves performance by reducing overhead during pipeline event processing, especially beneficial in environments with high pipeline activity. It streamlines change request creation by attaching all relevant evidence efficiently at pipeline completion, enhancing accuracy and reducing processing delays. Customers should carefully manage toggle changes to avoid pipeline interruptions and ensure evidence completeness.  
Reduce instance overhead by skipping step-level pipeline processing for accelerated change management and evidence collection for GitHub Actions, Azure DevOps (ADO), Jenkins and GitLab orchestration tools.

All relevant evidence in the pipeline is attached to the change request using import request instead of webhook notifications.

## Enable import based evidence collection {#import-based-evidence-collection-for-orchestration-capability__section_qzn_ybr_pfc}

You can enable this feature by switching on the Import based evidence collection for orchestration capability toggle in the Properties page. For more information, see [DevOps Change Velocity properties](https://www.servicenow.com/docs/Cy67V7Lf9sOXU2beB3VARQ "Use these properties to configure settings in the DevOps Change Velocity application.").  
Switching the toggle modifies how the pipeline events are processed. When switched on, the setting reduces instance overhead by skipping step-level processing in the pipeline. The skipped step-level events are ignored with the processing details, "IGNORED: This event is ignored because the 'Import based evidence collection for orchestration capability' property is enabled". Conversely, switching off reverts to the standard mode, where all inbound events undergo processing.  
Note:  
Ensure that no pipeline is running before making changes to this setting. Switching the toggle during an active pipeline execution may cause the pipeline to hang and eventually time out, resulting in incomplete or incorrect data collection. If a change request has already been created, you must cancel it manually, as required evidence may not be attached. Select Save to continue, and initiate a new pipeline execution after switching the toggle.

## How is the evidence collected {#import-based-evidence-collection-for-orchestration-capability__section_sy5_1xn_tfc}

When the change step in a pipeline is triggered, a callback record is created with the state: created and change evidence status: pending. An import request, with the corresponding import request pages is created to gather pipeline execution details and the required evidence. The change
request is then created with all the evidence attached to it. In addition, the import based evidence collection feature is triggered again at the pipeline completion event to ensure all the associated evidence is accurately
retrieved and associated with the change request. Post-creation of the change request, the auto-approval mechanisms, and subsequent behaviors remains the same as the existing behavior.  

For ADO
:
    * For build pipeline, when the property is enabled, the evidence collection happens based on the pipeline completion event only (step level events aren't processed to reduce the instance overhead).
    * For release pipeline, even if the property is enabled, the evidence collection happens based on processing step-level events.
    {#import-based-evidence-collection-for-orchestration-capability__ul_pgk_z5n_tfc}

For GitHub Actions
:
    * When the property is enabled, the evidence collection happens based on the workflow completion event only (step level events aren't processed to reduce the instance overhead).
    * If you're using GitHub Actions Deployment Gates in any of your steps, then you must configure the GitHub app, and the evidence collection happens based on the workflow completion event. For more information on deployment gates, see [GitHub Deployment Gates for ServiceNow DevOps Change](https://www.servicenow.com/docs/iT0hbTAFcNhfJfjBQ3WkrQ "Use the GitHub Deployment Gate capability to decide on whether a new deployment should proceed or halt.").
    {#import-based-evidence-collection-for-orchestration-capability__ul_isr_kzr_zfc}

Jenkins
:   When the property is enabled, the evidence collection happens based on the pipeline completion event only (step level events aren't processed to reduce the instance overhead).  
    Note:  
    You must install the latest Jenkins from the Jenkins Marketplace. Navigate to Manage Jenkins \> System configuration \> Plugins in your Jenkins instance. Search for ServiceNow DevOps Plugin and select it, and then select Install.

GitLab
:   When the property is enabled, the evidence collection happens based on the Pipeline events webhook event only (step level events aren't processed to reduce the instance overhead).

## Key points {#import-based-evidence-collection-for-orchestration-capability__section_byw_zfr_pfc}

* Import based evidence collection supports all existing pipeline styles (reruns, parallel, sequential) and configurations for GitHub Actions, Jenkins, and ADO.
* All types of evidence collection supported for GitHub Actions, ADO, GitLab, and Jenkins in the base system are also supported when this property is enabled.
* For GitHub Actions, environment-based change isn't supported.
* For GitLab, manual jobs (when: manual) are not supported.  
  For example,

       run_tests:
        script: npm test
        when: manual
        allow_failure: true

* For Jenkins, Freestyle pipelines are not supported.
* Historical import and polling features works the same way regardless of the Import based evidence collection for orchestration capability property being enabled or turned off.
* Restarting import in the import request record is also supported.
* Troubleshooting and error handling frameworks remain unaffected.
* If you're upgrading, the Import based evidence collection for orchestration capability property is turned off by default.
{#import-based-evidence-collection-for-orchestration-capability__ul_csv_kyk_pfc}