Skip to content
NexusBook a demo

ITSM & Engineering integration

Hand off from ServiceNow to Jira without losing the thread.

Incidents and changes that need engineering become Jira issues with the right context. Status and comments return to ServiceNow, and closure is recorded on both sides.

Discuss this integration All integration patterns

The problem

Why ServiceNow + Jira needs a governed process

Service desks escalate to engineering by copying details into another tool. Updates stop flowing back, customers wait, and closure in one system does not close the other.

Responsibility

How the systems divide responsibility

Service management record

ServiceNow

Incidents, tickets, change requests, CMDB items and service users.

Engineering work record

Jira

Issues, projects and engineering assignees.

Capabilities

What Nexus orchestrates

Pre-built action groups used in this pattern. Anything else runs through an API, protocol or database step, or Rules + Code, in the same workflow.

ServiceNow

55 ACTIONS

  • Incidents12
  • Tickets10
  • Change Management10
  • CMDB12
  • Users10

Jira

36 ACTIONS

  • Issues15
  • Projects10
  • Users11

Architecture

One governed run across both systems

Trigger: ServiceNowIntegration: ServiceNow + JiraRules + CodeHuman ApprovalSystem Action: JiraAudit

How work starts

ServiceNow and Jira

Both ServiceNow and Jira are trigger sources. A ServiceNow update can start the escalation, and a Jira update can start the return leg.

When a pre-built action does not cover it

Pre-built ActionAPI / Protocol / DBRules + Code

Workflow patterns

What teams run across ServiceNow + Jira

01

Incident escalation to engineering

An incident assigned to an engineering group creates a Jira issue in the mapped project, with CMDB context attached.

02

Status and comment handoff

Jira status changes and comments are posted back to the ServiceNow incident so the service desk sees progress.

03

Change request to engineering tasks

An approved ServiceNow change creates the Jira work needed to implement it, linked back to the change.

04

Coordinated closure

When the Jira issue is resolved, the incident moves to resolved with the engineering note, pending service owner confirmation.

Direction and ownership

Which way each change moves

Escalations flow from ServiceNow to Jira. Progress and resolution flow from Jira back to ServiceNow. Each system keeps its own workflow states.

  • ServiceNow Jira

    Incident or change context, affected CMDB items and priority.

  • Jira ServiceNow

    Issue status, comments and resolution for the linked incident or ticket.

Control

Approvals and exception handling

Human approval

A service owner confirms escalation into engineering for priorities your policy defines. Closure of customer-facing incidents can require confirmation before the ServiceNow state changes.

Exceptions

  • Unknown project or component mappings route to a triage queue.
  • Write failures on either side are retried and surfaced, never dropped.
  • Loop protection prevents an update echoing between the two systems.

Security, audit and deployment

Every run leaves a reviewable record

  • The originating incident or change and its priority.
  • Mapping rules applied and the Jira issue created.
  • Each status and comment synchronised, with timestamps.
  • Who confirmed escalation and closure.

Credentials for ServiceNow and Jira are held in the vault and used only by the steps that need them. Role-based permissions decide who can edit, approve and run the workflow. Nexus runs on premises, in private cloud or air-gapped, so the execution record stays inside your deployment boundary. Governance and audit

Participating connectors

The connectors behind this pattern

ITSM / Support

ServiceNow connector

55 pre-built actions · Trigger source: ServiceNow

View connector

ITSM / Support

Jira connector

36 pre-built actions · Trigger source: Jira

View connector

Related

Continue from here

FAQ

ServiceNow + Jira questions

Can either system start the run?
Yes. ServiceNow and Jira are both trigger sources, so each direction can start from its own system.
Does Nexus map every field automatically?
No. Mappings between incident and issue fields are agreed with both owners and kept in the workflow, where they can be reviewed.
How are update loops avoided?
The workflow records the origin of each change and ignores updates it wrote itself.

Integration review

Discuss this integration

Bring your ServiceNow and Jira process. We will map ownership, approval and the steps each system needs.

Discuss this integration Book a demo