# Jira ServiceNow Integration

Integrate Jira and ServiceNow to synchronize incidents, problems, service requests, bugs, and tasks across ITSM and DevOps teams using ZigiOps - a secure, no-code integration platform.

This integration enables real-time or scheduled data synchronization, eliminates manual updates, and ensures a single source of truth between Jira and ServiceNow.

<div><figure><img src="/files/EyDNKRlA3aitielNQHlW" alt=""><figcaption></figcaption></figure> <figure><img src="/files/7Nmi6AupG6zat84GUfVJ" alt=""><figcaption></figcaption></figure> <figure><img src="/files/xdd3TBeuEhqZAFU9pikD" alt=""><figcaption></figcaption></figure> <figure><img src="/files/Pw4QNXqJZsNwqcIP79DT" alt=""><figcaption></figcaption></figure></div>

### Integration video

{% embed url="<https://youtu.be/20AwIMqIgM0?si=psepxFoKv_KKLY4c>" %}

***

### What can I integrate between Jira and ServiceNow?

ZigiOps can integrate any Jira issue type (Tasks, Issues, Comments, etc.) with any ServiceNow entity (Incidents, Changes, CMDBs, etc.), allowing you to build custom workflows tailored to your processes and data models.

Out of the box, ZigiOps provides ready-made integration templates for the most common and widely used Jira and ServiceNow scenarios, including:

* Jira Tasks to ServiceNow Incidents
* ServiceNow Incidents to Jira Tasks
* ServiceNow Problems to Jira Bugs
* ServiceNow Service Catalog Tasks to Jira Tasks

These templates serve as preconfigured starting points and can be customized or extended to support additional Jira issue types, ServiceNow tables, and business-specific workflows. Each integration scenario can be configured as one-way or bi-directional, with full control over field mappings, filters, triggers, and synchronization rules.

| Common ServiceNow entities | Common Jira issue types | Common fields typically synchronized                                                                                                |
| -------------------------- | ----------------------- | ----------------------------------------------------------------------------------------------------------------------------------- |
| Incident                   | Task / Issue            | Summary / Short description, Description, Priority, Status / State, Assignee, Comments, Attachments                                 |
| Change Request (CR)        | Issue / Task            | Summary, Description, Priority, Status / State, Owner / Assignee, Comments, Attachments                                             |
| Problem                    | Bug / Issue             | Summary, Description, Priority / Severity, Status / State, Assignee, Comments, Attachments                                          |
| Service Catalog Task       | Task / Issue            | Summary, Description, Priority, Status / State, Requested for / Reporter, Comments, Attachments                                     |
| CMDB (Configuration Items) | Issue (custom) / Task   | Name / Identifier, Description, Attributes (custom fields), Relationships (when applicable), Comments/Notes, Attachments (optional) |
| **Any ServiceNow table**   | **Any Jira issue type** | Standard + custom fields, Comments, Attachments, Status/State mappings, Correlation ID (recommended)                                |

> **Note:** ZigiOps supports synchronization of all standard and custom fields for Jira and ServiceNow. The table above lists only the most commonly used fields for clarity and illustration purposes.

***

### How does the Jira and ServiceNow integration work?

ZigiOps connects Jira and ServiceNow using their native APIs and acts as a secure integration layer between the two systems.

* No scripting or custom development required
* Configured entirely through the ZigiOps UI
* Supports polling- and event-based synchronization
* Does not permanently store transferred business data

The platform can be deployed on-premises or used as a cloud service, depending on your security and compliance requirements.

***

### Prerequisites and permissions

Before enabling the Jira and ServiceNow integration, ensure the following prerequisites are met. The prerequisites below apply to all Jira and ServiceNow integration scenarios. Scenario-specific behavior is handled at the mapping and workflow level.

| Integration Scenario                           | ServiceNow - Authentication | ServiceNow - Permissions                         | ServiceNow - Environment                                | Jira - Authentication | Jira - Permissions                                       | Jira - Environment                                             |
| ---------------------------------------------- | --------------------------- | ------------------------------------------------ | ------------------------------------------------------- | --------------------- | -------------------------------------------------------- | -------------------------------------------------------------- |
| Jira Tasks to ServiceNow Incidents             | Username + Password         | x\_ziw\_obm.admin, personalize\_read\_dictionary | ServiceNow (any supported version); Optional MID Server | Username + API Token  | Create / Read / Update issues; Access to target projects | Jira Software or Jira Service Management, Version 7.x or newer |
| ServiceNow Incidents to Jira Tasks             | Username + Password         | x\_ziw\_obm.admin, personalize\_read\_dictionary | ServiceNow (any supported version); Optional MID Server | Username + API Token  | Create / Read / Update issues; Access to target projects | Jira Software or Jira Service Management, Version 7.x or newer |
| ServiceNow Problems to Jira Bugs               | Username + Password         | x\_ziw\_obm.admin, personalize\_read\_dictionary | ServiceNow (any supported version); Optional MID Server | Username + API Token  | Create / Read / Update issues; Access to target projects | Jira Software, Version 7.x or newer                            |
| ServiceNow Service Catalog Tasks to Jira Tasks | Username + Password         | x\_ziw\_obm.admin, personalize\_read\_dictionary | ServiceNow (any supported version); Optional MID Server | Username + API Token  | Create / Read / Update issues; Access to target projects | Jira Software or Jira Service Management, Version 7.x or newer |

***

### Setup

Follow the steps below to enable the Jira and ServiceNow integration using a prebuilt ZigiOps template.

1. Log in to your ZigiOps instance.
2. Navigate to ZigiOps - Configurator.
3. Load the desired Jira and ServiceNow integration template.
4. Select the corresponding Integrated Systems (Jira and ServiceNow).
5. Click **Save** to continue.
6. Enable the integration using the slider button located in the middle section of the screen.

Once enabled, ZigiOps starts synchronizing data based on the configured mappings and rules.

***

### Mapping examples

Below are typical field-mapping examples used across the Jira and ServiceNow integration scenarios. Mappings can be customized per use case.

**Example: Jira Task to ServiceNow Incident**

| Jira field  | ServiceNow field                 | Advanced Field Mapping Example       |
| ----------- | -------------------------------- | ------------------------------------ |
| Summary     | Short description                | -                                    |
| Description | Description                      | -                                    |
| Priority    | Priority                         | -                                    |
| Status      | State                            | To Do - 1, In Progress - 2, Done - 6 |
| Assignee    | Assigned to                      | -                                    |
| Comments    | Work notes / Additional comments | -                                    |
| Attachments | Attachments                      | -                                    |

**Example: ServiceNow Incident to Jira Task**

| ServiceNow field                 | Jira field  | Advanced Field Mapping Example       |
| -------------------------------- | ----------- | ------------------------------------ |
| Short description                | Summary     | -                                    |
| Description                      | Description | -                                    |
| Priority                         | Priority    | -                                    |
| State                            | Status      | 1 - To Do, 2 - In Progress, 6 - Done |
| Assigned to                      | Assignee    | -                                    |
| Work notes / Additional comments | Comments    | -                                    |
| Attachments                      | Attachments | -                                    |

**Example: ServiceNow Problem to Jira Bug**

| ServiceNow field    | Jira field  | Advanced Field Mapping Example       |
| ------------------- | ----------- | ------------------------------------ |
| Short description   | Summary     | -                                    |
| Problem description | Description | -                                    |
| Severity            | Priority    | -                                    |
| State               | Status      | 1 - To Do, 2 - In Progress, 6 - Done |
| Work notes          | Comments    | -                                    |

**Example: ServiceNow Service Catalog Task to Jira Task**

| ServiceNow field  | Jira field    |
| ----------------- | ------------- |
| Short description | Summary       |
| Description       | Description   |
| Requested for     | Reporter      |
| Assignment group  | Project       |
| Catalog variables | Custom fields |

***

### What data can be synchronized?

ZigiOps supports synchronization of:

* Standard fields
* Custom fields
* Status / state transitions
* Comments
* Attachments
* Users and assignments (configurable)

Each field can be mapped independently for each direction.

***

### Frequently asked questions (FAQ)

<details>

<summary>Can I use one template for multiple projects or assignment groups?</summary>

Yes. Filters and conditions allow you to scope synchronization by project, assignment group, state, priority, or custom logic.

</details>

<details>

<summary>Is the integration bi-directional?</summary>

Yes. All scenarios support bi-directional synchronization, configurable per field.

</details>

<details>

<summary>How are update loops prevented?</summary>

ZigiOps uses correlation IDs and internal logic to prevent circular updates.

</details>

<details>

<summary>Do I need to write scripts or use APIs manually?</summary>

No. All configuration is done through the ZigiOps UI.

</details>

<details>

<summary>Can I start with one-way sync and later enable bi-directional sync?</summary>

Yes. Direction can be changed at any time.

</details>

<details>

<summary>Does ZigiOps store my Jira or ServiceNow data?</summary>

No. ZigiOps does not permanently store transferred business data.

</details>

***

### Related resources

* [How to connect Jira to ZigiOps](#)
* [How to connect ServiceNow to ZigiOps](#)
* [Data mapping fundamentals](#)
* [Jira and ServiceNow integration troubleshooting](#)


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.zigiwave.com/integration-catalog/jira-servicenow-integration.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.