# Jira Server Integration Guide | PagerDuty Configure bidirectional sync between Jira Server or Data Center issues and PagerDuty incidents, including field and state mapping. ## Jira Server + PagerDuty Benefits - Tackle critical service requests and accelerate incident resolution with bidirectional sync between Jira Server issues and PagerDuty incidents. - Populate out-of-the-box or custom issue fields, sync incident priority and notes, and configure state mapping between Jira and PagerDuty. - Jira Server users can leverage PagerDuty's integrations and [PagerDuty AIOps](/ai-automation/aiops/overview) functionality. - This integration also supports Jira Service Management. > **Jira Cloud Integration:** If you use Jira Cloud, see the [Jira Cloud integration guide](/integrations/jira-cloud). ## Requirements ### To Configure the Integration **In PagerDuty**: - This integration only works with Jira Server for PagerDuty customers on the following pricing plans: Professional, Business, Digital Operations (legacy), and Enterprise for Incident Management. - The Jira administrator configuring this integration must also be a user within the PagerDuty account with valid login credentials. **In Jira Server**: - To configure the integration, you must have Jira administrator permissions. - This integration is for Jira **Server** (self-hosted). You can find the current version compatibility and download the integration from the [Atlassian Marketplace](https://marketplace.atlassian.com/apps/1218226/pagerduty-for-jira-server/version-history#b306010). ### To Use the Integration **In PagerDuty**: - You must have a PagerDuty user license to use the integration. ## How It Works - Based on predefined rules set in Jira, when a PagerDuty incident performs a condition's action, a webhook is sent to Jira where it can create or update an issue. - When a Jira issue performs a predefined condition's action, a webhook is sent to PagerDuty where it can create or update an incident. ## Version This guide details configuration of the **[Jira Server V4.3.3](https://marketplace.atlassian.com/apps/1218226/pagerduty-for-jira-server-data-center/version-history)** integration. > **Looking for a Different Version?:** The [Jira Server v3](/integrations/jira-server/jira-server-v3) integration is also available. ## Integration Walkthrough ### In Jira Server 1. From the **Jira Administration** menu in the top right corner, click **Manage Apps**. 2. In the [Atlassian Marketplace](https://marketplace.atlassian.com/), search for **PagerDuty** and select the appropriate Jira Server download for your [service region](/get-started/service-regions): 3. **US Service Region**: [PagerDuty for Jira Server & Data Center](https://marketplace.atlassian.com/apps/1218226/pagerduty-jira-server-extension). 4. **EU Service Region**: [PagerDuty for Jira Server & Data Center (EU only version)](https://marketplace.atlassian.com/apps/1224902/pagerduty-for-jira-server-data-center-eu-only-version). 5. After installing, select **Manage Apps** from the left menu, select **PagerDuty**, and click **Configure**. 6. Click **Login with PagerDuty** and log in to connect your PagerDuty account. 7. Click **Connect Jira to PagerDuty** to open the next screen where you will configure your account. 8. Add the required fields for the Jira instance you are working in. Click **Save** when finished. - When entering URLs, always specify the protocol (`http` or `https`) in the field. If the protocol is not specified, the integration will use `http`. - **Authentication Requirements**: You must configure an integration user account in Jira with read/write access to all connected projects. This integration user can authenticate using one of two supported methods: - **Basic Authentication (Username/Password)**: Enter the integration user's Jira username and password directly into the configuration fields. - **Personal Access Token (PAT)**: Generate a Personal Access Token for the integration user in Jira, then paste the token into the designated field. > **SSO Not Supported:** SSO authentication is not supported. You must use either basic authentication credentials or a Personal Access Token for the integration user. #### Configure Automation Rules To configure automation rules via the PagerDuty web app, continue following the instructions below. To configure automation rules via API, see the [Jira Server Integration API documentation](https://developer.pagerduty.com/api-reference/YXBpOjI3NDgyNjk-pager-duty-jira-server-integration-api). 9. Configure automation rules to automatically trigger incidents, create issues, and keep status updates synchronized between PagerDuty and Jira. If you are already on the PagerDuty settings page, select the **Rules** tab and click **Create Rule**. If you are returning to configuration, navigate to **Manage Apps** → **PagerDuty** → **Configure** → **Rules** tab and click **Create Rule**. 10. Enter a **Rule name**, **Select PagerDuty service(s)**, **Select JIRA Project(s)**, **Select JIRA Issue Type(s)**, and optionally check the **Sync comments & notes** checkbox. 11. Check the following rule options based on your preferences: **Automatically create PagerDuty incidents from JIRA issues**: - **When issue matches JQL**: Enter your preferred JQL. Select whether you would like this rule to run **On issue create** and/or **On issue update**. - **Additional actions after incident is created** _(optional)_: Select your preferred actions. - Another form will auto-populate below, and you may choose to add multiple conditions based on your preferences. **Create JIRA issues from PagerDuty incidents**: - **Create issue when incident**: Select your preferred **incident action** that will generate a Jira issue. Optionally, specify the priority and/or urgency by selecting an option from the **AND priority is one of** and/or **AND urgency is** dropdowns. - **Create issue into project**: Select the **Jira project** where you would like PagerDuty incidents to generate Jira issues. Select the **Issue type** you would like generated, and if your Jira issue type has any required fields, set those required fields to populate by choosing **Additional actions on issue create (optional)**. - Another form will auto-populate below, and you may choose to add multiple conditions based on your preferences. **Automatically update Jira issue**: - **When PagerDuty incident has linked issue AND**: Select your preferred **incident action** that will update a Jira issue. Optionally, specify the priority and/or urgency by selecting an option from the **AND priority is one of** and/or **AND urgency is** dropdowns. - **Actions**: Select your preferred Jira issue action that will occur based on the condition specified above. - Another form will auto-populate below, and you may choose to add multiple conditions based on your preferences. **Automatically update PagerDuty incident**: - **When Issue status changes to**: Select your preferred **Jira status** that will update the PagerDuty incident. - **Actions**: Select your preferred **PagerDuty incident action** that will occur based on the condition specified above. - Another form will auto-populate below, and you may add multiple conditions based on your preferences. Click **Save** to save your rule(s). You should see the following webhook check dialog if the connection was successful: ![Dialog confirming the Jira webhook check completed successfully](/images/kb/366ddfa4d3cdb40f3451291d9818b1ca9754ba8ef935af0564c1624e60576046-jira-server-webhook-success-dialog.webp) *Webhook update summary* If you receive an unsuccessful webhook error, navigate back to the **Rules** tab and click **Check webhooks…** to troubleshoot the error. Once the webhook check has been successfully completed, proceed to the next section to link your PagerDuty and Jira accounts. #### Link PagerDuty and Jira User Accounts Linking PagerDuty and Jira user accounts allows the integration to identify which user changed an incident or issue. It also allows you to define who an incident or issue should be assigned to. If a user account is not linked and a Jira fallback user has not been configured (see step 17), the integration will not pick up those user-made changes. A Jira administrator can link user accounts, or individuals can link their own PagerDuty accounts between systems. - **To have a Jira administrator link the accounts**: Follow steps 14–17 below. - **To have individual users link their accounts**: Skip to step 18. 14. If you are still on the PagerDuty settings page, select the **User mapping** tab and skip to step 16. If you are returning to configuration, from the top right **Jira Administration** menu, select **Manage Apps**. 15. Select **Manage Apps** again from the left menu, click the **PagerDuty** add-on, then click **Configure**. 16. Under **PagerDuty settings**, click the **User mapping** tab and click **Link Users** to start mapping user accounts between systems. ![User mapping tab with a Link Users button to map PagerDuty and Jira accounts](/images/kb/e454e5da77368caa324ec0e855b9c2affe679bdf2c48c2ddedd2a37efbcf7f01-jira-server-user-mapping-new.webp) *User mapping configuration* 17. On this page you can also optionally map users based on email, and set a fallback user in the event that a user wants to take action on an incident but their account is not mapped. 18. **To have individual users link their accounts**, they will need to go to an issue in your Jira project and click the **Users** icon to link their user accounts. If the icon is orange, their user account is not linked. Once linked, the icon will appear grey. ![Jira issue with a Users icon a user clicks to link their PagerDuty account](/images/kb/0e67ee5550c6bd59144a76a927819aa776028128d4ae3f33f059785ec1b770cf-jira-server-connect-users.webp) *Incident details* Once your Jira and PagerDuty accounts have been linked, the integration is complete. #### Connect Multiple PagerDuty Accounts To connect multiple PagerDuty accounts, navigate to the **Account Integrations** page and click **Logout** at the bottom of the page. Click **Login with PagerDuty** and log in on the screen that appears to connect your PagerDuty account. You will need to complete the [Integration Walkthrough](#integration-walkthrough) steps 1–3 and complete the [Link PagerDuty and Jira User Accounts](#link-pagerduty-and-jira-user-accounts) section again based on your secondary account information. #### Connect Multiple Jira Accounts To add another Jira account, log in to the secondary Jira instance and complete the [Integration Walkthrough](#integration-walkthrough) steps 1–13. ### Jira Service Management Required Steps 1. If you are integrating PagerDuty with Jira Service Management, ensure that the PagerDuty user account in Jira has the necessary permissions. 2. For each of your Service Desk projects, ensure that the PagerDuty user account has **Service Desk Team** access: - From the **Jira Administration** menu in the top right corner, click **Projects**. - Select your Jira Service Management **project**. - Click the **Users and roles** tab under the Project settings navigation bar. - Select the **Add users to a role** button. - Add the `jira-servicedesk-users` group or **PagerDuty** user to the **Service Desk Team** role. You can learn more about managing users and roles in [Atlassian's documentation](https://confluence.atlassian.com/adminjiracloud/managing-project-roles-776636382.html). ## Migrate from Jira Server to Jira Cloud No automatic migration path is available at this time. To migrate from Server to Cloud: 1. Follow the instructions to configure the [Jira Cloud integration](/integrations/jira-cloud) with the necessary service mappings. Test the flow by following the [Jira Cloud User Guide](/integrations/jira-cloud/jira-cloud-user-guide). 2. [Uninstall your Jira Server integration](#uninstall-jira-server) once you have configured the Jira Cloud integration. ## Uninstall Jira Server 1. Navigate to **Integrations** → **Extensions** and click **Jira Server Extension** to the right of your extension. 2. Click **How to Uninstall**, follow the instructions listed, and click **Delete Configuration**. ## FAQ **Is this integration bidirectional?** Yes, you can create Jira issues from PagerDuty incidents and PagerDuty incidents from Jira issues. **What if my Jira Server is behind a firewall?** To allow bidirectional integration between PagerDuty and your Jira Server, you may need to configure your firewall to allow incoming traffic from PagerDuty. See [Safelist IPs](/account-admin/safelist-ips) for more information. You specifically need to safelist IPs for PagerDuty [webhooks](/account-admin/safelist-ips#webhooks), the [REST API](/account-admin/safelist-ips#rest-api), and specific IPs for [Jira Server](/account-admin/safelist-ips#jira-server-integration). **Does the Jira Server integration support mandatory custom fields?** Yes, you can have PagerDuty populate mandatory Jira fields. You can define them while [configuring](#configure-automation-rules) the **Create Jira Issues from PagerDuty incidents** settings. ![Mandatory custom field configuration](/images/kb/9377ffbb59c21a9b35809e1a771719bb1294df2ca8da3f7842556b5d4522ff77-jira-server-create-jira-issues-faq.webp) *Mandatory custom field configuration* **When testing, I don't see an incident or issue being created?** To troubleshoot, the Jira administrator can navigate to global settings , select **Manage Apps**, click the **PagerDuty** app, and click **Configure**. Select the **Debug logs** tab. With this window still open, open another tab or window in your browser and try to test the integration's workflow. Any errors or successes will appear in the debug logs as long as you keep the window open while testing. **When I update the PagerDuty incident's status, the Jira ticket isn't getting updated. What's happening?** This can happen for the following reasons: - The Jira project's workflow requires certain fields to be populated when setting it to that given state, and those fields are not populated. - The Jira project's workflow does not permit the transition between the issue states corresponding to the previous and current PagerDuty incident states. For instance, if your Jira workflow does not permit setting a **To-Do** status Jira ticket directly to **Done**, and the **Triggered** status in PagerDuty maps to **To-Do** while the **Resolved** status maps to **Done**, then if a triggered incident is resolved without acknowledging it first, the ticket will not move to the **Done** state because this modification is not permitted per your Jira project's configured workflow. One way to ensure the workflow configuration does not interfere is to edit the statuses corresponding to acknowledged and/or resolved, and enable transitions from all other statuses to it. ![Configure transition status](/images/kb/f2fb87a7764cd90039bcd2571c42d90bb09e17fee429dac01391b6bf1ef1e052-jira-server-remove-status.webp) *Configure transition status* **I just updated the priority of a PagerDuty incident, why didn't the priority update in the Jira issue?** The Jira issue is only updated when the PagerDuty incident triggers an action that would trigger a v2 webhook. A full list of actions can be viewed in [the webhook documentation](https://developer.pagerduty.com/docs/88922dc5e1ad1-overview-v2-webhooks#webhook-types). To request that PagerDuty trigger an action for PagerDuty incident priority changes, submit a feature request [with the Support Team](https://www.pagerduty.com/contact-us/#contact-support). **Can we turn off the PagerDuty sidebar app for projects that don't use PagerDuty?** You can disable the sidebar for a specific project by navigating to that project in Jira, clicking into **Project Settings** → **PagerDuty integration**, and toggling **off** next to **Show PagerDuty issue sidebar for this project**. **What happens to my workflow rules when I upgrade from another version to this version (4.x.x)?** If you upgrade from another version, all existing workflow rules are maintained in the PagerDuty web app. They will continue to use the PagerDuty integration user and can be edited in the PagerDuty web app. New rules can be created in Jira, and previously created rules will appear in a read-only format. To upgrade these rules to the v4 version, recreate them by [following steps 11–13](#configure-automation-rules). **What happens when the Jira user who set up the integration is removed from the Jira account?** You will need to reauthorize the integration by following steps 1–3 and steps 6–10 in the guide above. **In the Rules settings page, what happens if I use the toggle "Show PagerDuty sidebar on projects by default"?** When the toggle is switched to **OFF** for the first time: - The PagerDuty sidebar will continue to be displayed for connected projects. - The PagerDuty sidebar will be hidden for non-connected projects. - The PagerDuty sidebar will not be displayed for newly created projects until connected to a PagerDuty service or manually enabled in the project-level settings page. - A dialog box will appear to guide you through this bulk operation. When the toggle is switched to **ON**: - The PagerDuty sidebar will continue to be displayed for connected projects. - The PagerDuty sidebar will be displayed for non-connected projects. - New projects created after this operation will display the PagerDuty sidebar. When the toggle is switched to **OFF** for subsequent times: - The PagerDuty sidebar will continue to be displayed for connected projects. - The PagerDuty sidebar will be hidden for non-connected projects. - The PagerDuty sidebar will not be displayed for newly created projects until connected to a PagerDuty service or manually enabled in the project-level settings page. - A dialog box will not appear during this operation. **I have renamed a Jira Base URL in my Jira Server instance. How can I update the Jira Base URL on the PagerDuty side?** If you have renamed a Jira Base URL, or plan to do so, reach out to the [Support team](https://www.pagerduty.com/contact-us/#contact-support) to assist with the rename process.