> For the complete documentation index, see [llms.txt](https://docs.zigiwave.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.zigiwave.com/available-systems/jira.md). # Jira Learn how to connect Jira Software and Jira Service Management to ZigiOps. Step-by-step configuration, API token setup, correlation fields, and integration templates. ### What is Jira integration in ZigiOps? Jira is a widely used issue tracking and service management platform for DevOps and ITSM teams. ZigiOps enables secure, agentless, bi-directional integrations between Jira and ITSM, monitoring, CRM, and enterprise systems. ZigiOps connects to Jira Cloud using OAuth 2.0 (3LO) authorization. Jira Data Center and Server instances connect with Basic authentication. OAuth 2.0 lets you connect by signing in with your Atlassian account, with no passwords or API Tokens stored in the connected system settings. With ZigiOps, Jira can: * Receive incidents, alerts, and events from monitoring tools * Sync issues, tasks, bugs, and service requests * Participate in end-to-end ITSM and DevOps workflows * Support backward synchronization (updates flow both ways) ### Which Jira products and versions are supported? **Using a supported version is mandatory.** | Product | Supported Deployment Types | Supported Versions | | ----------------------- | -------------------------- | ------------------ | | Jira Software | All | 7.x (or newer) | | Jira Service Management | All | 7.x (or newer) | ### Which authentication methods does ZigiOps support for Jira? ZigiOps supports two authentication methods for Jira. Choose the one that matches your deployment type and security requirements. | Criteria | OAuth 2.0 (3LO) | Basic (API Token or password) | | ----------------------------- | ---------------------------------------------------------------------- | ------------------------------------------------------------------------ | | Supported deployment | Jira Cloud | Jira Cloud, Data Center, Server | | How you sign in | Atlassian account login and consent screen | Username plus API Token or password | | Credentials stored in ZigiOps | Access and refresh tokens only | Username and API Token or password | | Token renewal | Automatic, using a refresh token | Manual, when the API Token expires or is revoked | | CAPTCHA lockouts | Not affected | Possible after repeated failed logins | | Best for | Fast, secure setup of Jira Cloud and the default integration templates | On-premises Jira and advanced use cases beyond the OAuth app permissions | ### Are there any environmental prerequisites for Jira? Before configuring Jira, always confirm the prerequisites of the corresponding integration template, as some templates may not require all steps described below. See the **Related Templates** section at the end of this page. **OAuth 2.0 prerequisites (Jira Cloud only):** * An Atlassian account with access to the Jira Cloud site you want to connect. * Jira permissions that cover the integration use case. If the account lacks the permissions requested by the ZigiWave OAuth app, Jira returns an “Access denied” message at the end of the authorization flow. * Outbound HTTPS access from ZigiOps to `https://auth.atlassian.com` and `https://api.atlassian.com`. **Basic authentication prerequisites:** * A Jira user account for the integration. * An API Token or password. #### How do I create an API Token in Jira Cloud? An API Token is required when you connect Jira Cloud to ZigiOps with Basic authentication. If you use OAuth 2.0, skip this section. {% stepper %} {% step %} Log in to your Jira instance Log in to your Jira instance using the Atlassian account intended for integration. {% endstep %} {% step %} Open the Atlassian API Token page Open the Atlassian API Token page: `https://id.atlassian.com/manage-profile/security/api-tokens`
{% endstep %} {% step %} Create the token Click **Create API Token**.
{% endstep %} {% step %} Copy and store it securely Copy and store the token securely. The token is visible **only once** after creation.
{% endstep %} {% endstepper %} ### How do I create a correlation field in Jira? Correlation fields allow ZigiOps to track and synchronize records across systems. {% stepper %} {% step %} Log in to Jira Log in to your Jira instance. {% endstep %} {% step %} Open Custom Fields Navigate to: **Administration - Issues - Custom Fields**
{% endstep %} {% step %} Create a new field Click the **Create new field** button in the upper right corner. {% endstep %} {% step %} Configure the field Create a new custom field: * **Type:** Text Field (single line) * **Name:** Correlation ID (or another suitable name)
{% endstep %} {% step %} Edit the field Navigate to **Edit Field**.
{% endstep %} {% step %} Associate the field Associate the field with: * Create Issue Screen * Edit Issue Screen * View Issue Screen (for the relevant projects)
{% endstep %} {% step %} Update the integration template Update your integration template in ZigiOps to replace the default correlation field with the newly created one.
{% endstep %} {% endstepper %} ### How do I connect Jira Cloud to ZigiOps with OAuth 2.0? OAuth 2.0 is the fastest and most secure way to connect Jira Cloud to ZigiOps. You sign in with your Atlassian account and approve the ZigiWave OAuth app. ZigiOps then handles the access token, refresh token, and Jira Cloud ID automatically. {% stepper %} {% step %} Log in to ZigiOps. Log in to your ZigiOps instance. {% endstep %} {% step %} Open the Jira connected system setup. Navigate to: Connected Systems - Add New System - Jira {% endstep %} {% step %} Select OAuth 2.0. In the **Authentication Type** field, select **OAuth 2.0**. {% endstep %} {% step %} Sign in with your Atlassian account. ZigiOps redirects you to the Atlassian login page. Log in with the Atlassian account you want to use for the integration. {% endstep %} {% step %} Choose your Jira site. If your Atlassian account has access to more than one Jira Cloud site, select the one you want to connect. {% endstep %} {% step %} Accept the permissions. Review the permissions requested by the ZigiWave OAuth app and click **Accept**. {% endstep %} {% step %} Confirm the connection. Atlassian redirects you back to ZigiOps. The connection is complete, and Jira becomes available in your integration templates. {% endstep %} {% endstepper %} ZigiOps sends OAuth 2.0 requests to the Atlassian API gateway (`https://api.atlassian.com/ex/jira/{cloudId}/...`) instead of your site URL (`https://your-domain.atlassian.net`). ZigiOps retrieves the Cloud ID of your Jira site automatically, so you don’t need to enter it. #### What permissions does the ZigiWave OAuth app request? The ZigiWave OAuth app requests the scopes below. They cover the use cases supported by the default Jira integration templates. For advanced scenarios outside these scopes, use Basic authentication. | Scope | What it allows ZigiOps to do | | --------------------------------------------------- | ------------------------------------------------------------------------------------------------ | | read:jira-work, write:jira-work | Read, create, and update issues, comments, and attachments | | read:jira-user | Read user details, for example to map assignees and reporters | | manage:jira-project | Read and manage project-level settings used in mappings | | manage:jira-configuration | Access Jira configuration such as fields and issue types | | manage:jira-webhook | Register and manage webhooks for event-driven synchronization | | manage:jira-data-provider | Manage development and operations data linked to issues | | read:servicedesk-request, write:servicedesk-request | Read, create, and update Jira Service Management requests | | manage:servicedesk-customer | Manage Jira Service Management customers | | offline\_access | Obtain a refresh token so ZigiOps renews access automatically without asking you to log in again | ### How do I connect Jira Software to ZigiOps with Basic authentication? #### Jira Software - Connected System Configuration Follow the steps below to add Jira Software as a connected system. {% stepper %} {% step %} Log in to ZigiOps Log in to your **ZigiOps** instance. {% endstep %} {% step %} Open the Jira connected system setup Navigate to: **Connected Systems - Add New System - Jira** {% endstep %} {% step %} Configure the parameters Configure the following parameters: * **Authentication Type** - Select **Basic**. * **Server URL** - Example: `https://name.atlassian.net` * **Username** - Jira username or Atlassian account email * **Password** - User password or API Token * **Proxy Settings** (optional) - Enable if a proxy server is required {% endstep %} {% step %} Save the settings Review the settings and click **Save**. {% endstep %} {% endstepper %} ### How do I connect Jira Service Management to ZigiOps? Jira Service Management requires an additional configuration step. You can connect Jira Service Management Cloud with OAuth 2.0 or Basic authentication. If you use OAuth 2.0, complete the steps in the OAuth 2.0 section above instead of steps 1 to 4 below, then continue with steps 5 to 7 to enable the JiraSD option. #### Jira Service Management - Connected System Configuration {% stepper %} {% step %} Log in to ZigiOps Log in to your **ZigiOps** instance. {% endstep %} {% step %} Open the Jira connected system setup Navigate to: **Connected Systems - Add New System - Jira** {% endstep %} {% step %} Configure the parameters Configure the following parameters: * Authentication Type - Select Basic * **Server URL** - Example: `https://name.atlassian.net` * **Username** - Jira Service Management user * **Password** - Password or API Token * **Proxy Settings** (optional) {% endstep %} {% step %} Save the system Click **Save** to store the system. {% endstep %} {% step %} Open advanced settings Open **Options - Advanced Settings**. {% endstep %} {% step %} Enable JiraSD Enable the **JiraSD** option. {% endstep %} {% step %} Apply the changes Click **Apply**. {% endstep %} {% endstepper %} This setting ensures proper handling of Jira Service Management entities such as requests and service desk tickets. ### How do I manage or reconnect a Jira OAuth 2.0 connection? **Token renewal:** ZigiOps uses a refresh token to renew access automatically, so your integrations keep running without manual reconnection. **Reconnecting:** If the authorization fails or is revoked in Atlassian, open the Jira system in ZigiOps and click **Get New Access Token** *(verify label)* to restart the OAuth flow. **“Access denied” message:** This appears at the end of the authorization flow when the Atlassian account lacks the permissions requested by the ZigiWave OAuth app. Grant the account the required Jira permissions, or sign in with a different account, then retry. **Adding or deleting a system:** Each new Jira system always requires a fresh authorization. When you delete a Jira system, ZigiOps closes its OAuth connection and invalidates its tokens. **Switching methods:** Basic authentication stays available for every Jira system. You can switch to it for advanced use cases that the OAuth app permissions don’t cover. ### What are the most common Jira integration use cases? #### **Use Case 1: Incident escalation from monitoring tools to Jira** When a critical alert is detected in a monitoring system (such as infrastructure or application monitoring), ZigiOps can automatically create or update a Jira issue. The alert details, severity, timestamps, and related metadata are mapped directly into Jira tasks or bugs. As the incident is acknowledged or resolved in Jira, updates can be synchronized back to the source system, ensuring full visibility and closed-loop incident management. #### **Use Case 2: Bi-directional ITSM workflows between ServiceNow and Jira** Many organizations use ServiceNow for IT operations and Jira for development teams. With ZigiOps, incidents or service requests created in ServiceNow can automatically generate Jira tasks or bugs, including comments, attachments, and priority changes. Updates made by developers in Jira are synchronized back to ServiceNow, eliminating manual handoffs and status mismatches between teams. #### **Use Case 3: Centralizing DevOps work from multiple tools into Jira** Jira is often used as the central system for tracking development and operational work. ZigiOps enables tasks, issues, and events from tools like Azure DevOps, monitoring platforms, or CRM systems to be consolidated into Jira. This allows teams to manage all incoming work in a single Jira project while maintaining traceability back to the original source system. ### What integration templates are available for Jira? ZigiOps provides a wide range of prebuilt Jira integration templates, organized by system pair. | Template | Direction | | --------------------------------------------- | -------------- | | Azure DevOps tasks - Jira tasks | Bi-directional | | Cherwell incidents - Jira tasks | Bi-directional | | Freshdesk tickets - Jira tasks | Bi-directional | | Jira tasks - Remedy incidents | Bi-directional | | Jira tasks - Remedy problems | Bi-directional | | Jira tasks - Salesforce cases | Bi-directional | | Jira tasks - ServiceNow incidents | Bi-directional | | Microsoft Dynamics incidents - Jira tasks | Bi-directional | | OBM events - Jira tasks | Bi-directional | | PagerDuty incidents - Jira tasks | Bi-directional | | Remedy change requests - Jira tasks | Bi-directional | | Remedy incidents - Jira tasks | Bi-directional | | Remedy problems - Jira tasks | Bi-directional | | Remedy work orders - Jira tasks | Bi-directional | | Salesforce cases - Jira tasks | Bi-directional | | ServiceNow incidents - Jira tasks | Bi-directional | | ServiceNow problems - Jira bugs | Bi-directional | | ServiceNow service catalog tasks - Jira tasks | Bi-directional | | SolarWinds alerts - Jira tasks | Bi-directional | Each template includes field mappings, direction of synchronization, and entity-specific logic. For detailed information about available templates for Jira integrations, please contact: \ **Email:** ### Jira OAuth 2.0 FAQ **Does ZigiOps support OAuth 2.0 for Jira?**\ Yes. ZigiOps supports OAuth 2.0 (3LO) authorization for Jira Cloud, including Jira Software and Jira Service Management. **Can I use OAuth 2.0 with Jira Data Center or Server?**\ No. OAuth 2.0 (3LO) is an Atlassian Cloud feature. Connect Jira Data Center and Server with Basic authentication. **Do I need an API Token to connect Jira with OAuth 2.0?**\ No. With OAuth 2.0, you sign in with your Atlassian account and approve the ZigiWave OAuth app. No API Token or password is needed. **Do I have to log in again when the access token expires?**\ No. ZigiOps renews the access token automatically using a refresh token. **Why should I use OAuth 2.0 instead of Basic authentication?**\ OAuth 2.0 is more secure, because no passwords or API Tokens are stored. It also avoids the CAPTCHA lockouts that can block Basic authentication after failed login attempts. ### Summary The Jira integration in ZigiOps enables: * Agentless, secure connectivity * Support for Jira Software and Jira Service Management * OAuth 2.0 (3LO) authorization for Jira Cloud and API Token-based Basic authentication * Correlation-aware synchronization * Prebuilt templates for ITSM, DevOps, and monitoring use cases --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.zigiwave.com/available-systems/jira.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.