PagerDuty Jira Service Management

Update tickets when an incident is resolved

When an incident is resolved in PagerDuty, add a note to the related tickets in Jira Service Management.

Try:

See all PagerDuty + Jira Service Management integrations or talk to a human

Trusted by teams already building on Knit·4.9 out of 5 stars4.9/5 on G2·GoogleGoogle for Startups Accelerator
prismforceHackerearthIsotopes AIInfojobsPayoneerOutsolveSkuadPayworksItiliteOnsurityRazorpayXMultiplierPeoplestrongScrutCeipal

How Knit builds this workflow

The Agent researches both APIs and wires the trigger on one side to the action on the other — no pre-built connector required. Here is the vocabulary it has to work with.

PagerDuty Explore PagerDuty →

Triggers
New alert

Fires when a monitor or check in PagerDuty raises an alert.

New or updated incident

Fires when an incident is opened or updated in PagerDuty.

Monitor state changed

Fires when a monitored site, service or alarm in PagerDuty changes state.

Actions
Create incident

Opens a new incident or alert in PagerDuty.

Acknowledge incident

Acknowledges an open incident in PagerDuty.

Resolve incident

Resolves an incident in PagerDuty.

Jira Service Management Explore Jira Service Management →

Triggers
New ticket or conversation

Fires when a new support ticket or chat conversation starts in Jira Service Management.

Ticket status changed

Fires when a ticket's status changes in Jira Service Management.

Ticket assigned

Fires when a ticket in Jira Service Management is assigned to an agent.

SLA breached

Fires when a ticket in Jira Service Management breaches its response SLA.

Actions
Create ticket

Creates a new ticket in Jira Service Management.

Update ticket status

Updates a ticket's status in Jira Service Management.

Assign ticket

Assigns a ticket in Jira Service Management to an agent.

Reply to a ticket or chat

Posts a reply or internal note on a ticket or conversation in Jira Service Management.

Open an incident from an urgent ticket When an urgent ticket is created in Jira Service Management, create an incident in PagerDuty. See details
Create a tracking ticket for each alert When PagerDuty raises a new alert, create a ticket in Jira Service Management so it is tracked to closure. See details

See all PagerDuty + Jira Service Management integrations →  ·  Browse the full workflow library →

Enterprise-grade security

SOC 2 certified GDPR compliant ISO 27001 certified
Visit our Security Center Review the DPA
FAQ

Common questions

Can Knit build “Update tickets when an incident is resolved” between PagerDuty and Jira Service Management?

Yes — describe it in the box above and Knit's Integrations Agent researches PagerDuty and Jira Service Management's public API docs (or your own uploaded docs) and builds a working workflow, whether or not either app already has a pre-built connector.

How long does it take to build?

Minutes to a first working version, not weeks — you test it against real data before it goes anywhere near production.

Why connect incident management to a helpdesk?

When something breaks, tickets pile up in Jira Service Management. Linking them to the incident in PagerDuty keeps support informed and avoids duplicate investigation.

Can a ticket open an incident?

Yes. When a ticket in Jira Service Management reports an outage, you can create an incident in PagerDuty for the on-call team.

Put Integrations on Autopilot. Talk to Experts.

Knit is loved by customers across the globe due to our seamless product and white glove support. You'll love us too!

Talk to a Human