User story integration

concept brazil Updated Jun 3, 2026 2 min read user-story-integration-properties.md
Raw file servicenow.com

The User story integration creates agile tasks and stories directly from Scan Engine finding records in ServiceNow, Jira, Azure DevOps, or any external system.

When a finding is identified, the integration can automatically or manually generate a work item in your agile system of record. Role required: sn_se.scan_engine_admin.

Configure the ServiceNow user story integration on the source instance where the findings originate. The integration creates stories in the target instance, such as production, from those findings. Define both instances in My SN Instances.

Configure Jira, Azure DevOps, or the Other type on the instance where Scan Engine runs and the findings are generated. Those types don't need a My SN Instances record.

Type Authentication Description
ServiceNow instance My SN Instances + OAuth or Basic Creates stories in a Production instance from sub-production findings using Agile 2.0.
Jira Basic auth record + API token Creates work items in a Jira project from findings.
Azure DevOps Basic auth record + API token Creates work items in an Azure DevOps project from findings.
Other Username and API token on Scan Engine Properties Connects to any external system via a custom payload script.

Note: Jira and Azure DevOps authenticate with a Basic auth record and an API token, configured in Scan Engine Properties. The Other type takes a username and API token directly on Scan Engine Properties. None of these types use My SN Instances.

Parent Topic:Scan Engine integrations

Related topics

Configure ServiceNow user story integration

Configure Jira user story integration

Configure Azure DevOps story integration

Configure other integration options

Search documentation
Search document titles and file paths on the brazil branch