• Give responders the context they need to act fast with an enhanced sidebar that includes a full timeline and incident notes
• Ack & own with synced user accounts between PagerDuty and Jira. Prevent miscommunications before they stop with a fallback user and get resolution updates in real-time every time
• Configure advanced workflows that let you take actions in both systems at once across teams
• Scale your business with many (PD) to many (Jira) connections
• Give the right people the right information with advanced visibility settings

Get started with the integration by creating a free account, and using this installation guide.

• Give responders the context they need to act fast with an enhanced sidebar that includes a full timeline and incident notes
• Ack & own with synced user accounts between PagerDuty and Jira. Prevent miscommunications before they stop with a fallback user and get resolution updates in real-time every time
• Configure advanced workflows that let you take actions in both systems at once across teams
• Scale your business with many (PD) to many (Jira) connections
• Give the right people the right information with advanced visibility settings

Get started with the integration by creating a free account, and using this installation guide.

Bug fixes and 8.2 Compatibility

Bug fixes and 8.2 Compatibility

• Added Data Center Support

Add support for Jira Data Center

• Compatible with Jira Server 8.0
• Bug fixes

• Improvements to how notes are synchronized and PagerDuty incident titles
• Bug fixes

• Pick which PagerDuty account is used for note sync from Jira to PagerDuty
• Ability for PagerDuty to populate single-select, multi-select, label and user fields in Jira (when building a field mapping)
• Field & Priority mapping now respects project-specific configuration schemes, if used
• Other bug fixes

Note: if you run into problems with PagerDuty not being able to populate certain custom fields successfully, delete the mapping and re-create it.

• Ability for PagerDuty to populate Jira fields
• Automatic and Manual sync from PagerDuty to Jira
• Priority sync between PagerDuty and Jira
• Notes sync from PagerDuty to Jira
• Map PagerDuty Acknowledge state to a Jira state

This version fixes an issue where the add-on did not automatically trigger the creation of PagerDuty incidents based on JQL which included JIRA priority

This version of the add-on fixes an issue where the "Create JIRA issue" button in PagerDuty was not working when the issue title was longer than 255 characters.

This version fixes a couple of issues that were recently reported:

1. Fixes an issue with the default priority not being set on JIRA issues created by PagerDuty2. Fixes an issue where the "Create JIRA issue" button was not working for some services in PagerDuty

This version fixes an issue with permissions.

Get started with our PagerDuty Jira Server Extension Guide

Features of this add-on include i) Ability to create a Jira issue from PagerDuty & ability to create PagerDuty incidents from Jira ii) Linked PagerDuty incident information shown inside Jira issues iii) Optional, real-time status synchronization

What's new in this version? This version now supports Data Center.

Get started with our PagerDuty Jira Server Extension Guide

Features of this add-on include i) Ability to create a Jira issue from PagerDuty & ability to create PagerDuty incidents from Jira ii) Linked PagerDuty incident information shown inside Jira issues iii) Optional, real-time status synchronization

What's new in this version?

We now support the ability to automatically create PagerDuty incidents from JIRA using JIRA JQL. For example you might want a PagerDuty incident created when a high-priority JIRA ticket is created for a particular person. To use this feature, enter the JQL in the PagerDuty configuration screen.

Get started with our PagerDuty Jira Server Extension Guide

Features include i) Ability to create a Jira issue from PagerDuty & ability to create PagerDuty incidents from Jira ii) Linked PagerDuty incident information shown inside Jira issues iii) Optional, real-time status synchronization