# Jira Azure DevOps Integration

Integrate Jira and Azure DevOps to synchronize work items, tasks, bugs, and issues across DevOps and project management 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 Azure DevOps.

<figure><img src="/files/Hl6qbEgicdT2mkQgF63X" alt=""><figcaption></figcaption></figure>

<figure><img src="/files/pOUt0aVAZfhPsWrdxxJE" alt=""><figcaption></figcaption></figure>

### **Integration video**

{% embed url="<https://youtu.be/-HN2CsFW-Qg?si=y_GWqK0lDRctRTDQ>" %}

***

### What can I integrate between Jira and Azure DevOps?

ZigiOps can integrate any Jira issue type (Tasks, Bugs, Epics, Stories, etc.) with any Azure DevOps work item type (Tasks, Bugs, User Stories, Epics, 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 Jira and Azure DevOps scenarios, including:

* Jira Tasks to Azure DevOps Tasks
* Azure DevOps Tasks to Jira Tasks
* Jira Bugs to Azure DevOps Bugs
* Azure DevOps Work Items to Jira Issues

These templates serve as preconfigured starting points and can be customized or extended to support additional issue types, work item types, 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 Azure DevOps entities    | Common Jira issue types | Common fields typically synchronized                                                                 |
| ------------------------------- | ----------------------- | ---------------------------------------------------------------------------------------------------- |
| Task                            | Task / Issue            | Title / Summary, Description, Priority, Status / State, Assignee, Comments, Attachments              |
| Bug                             | Bug / Issue             | Title / Summary, Description, Priority, Severity, Status / State, Assignee, Comments, Attachments    |
| User Story                      | Story / Issue           | Title / Summary, Description, Priority, Status / State, Assignee, Comments, Attachments              |
| Epic                            | Epic                    | Title / Summary, Description, Priority, Status / State, Owner / Assignee, Comments, Attachments      |
| Any Azure DevOps work item type | Any Jira issue type     | Standard + custom fields, Comments, Attachments, Status/State mappings, Correlation ID (recommended) |

{% hint style="info" %}
ZigiOps supports synchronization of all standard and custom fields for Jira and Azure DevOps. The table above lists only the most commonly used fields for clarity and illustration purposes.
{% endhint %}

***

### How does the Jira and Azure DevOps integration work?

ZigiOps connects Jira and Azure DevOps 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 Azure DevOps integration, ensure the following prerequisites are met. The prerequisites below apply to all Jira and Azure DevOps integration scenarios. Scenario-specific behavior is handled at the mapping and workflow level.

| Integration Scenario             | Jira - Authentication | Jira - Permissions                                       | Jira - Environment                                             | Azure DevOps - Authentication | Azure DevOps - Permissions                        | Azure DevOps - Environment                           |
| -------------------------------- | --------------------- | -------------------------------------------------------- | -------------------------------------------------------------- | ----------------------------- | ------------------------------------------------- | ---------------------------------------------------- |
| Jira Tasks to Azure DevOps Tasks | Username + API Token  | Create / Read / Update issues; Access to target projects | Jira Software or Jira Service Management, Version 7.x or newer | Username + PAT                | Read / Write work items; Access to target project | Azure DevOps (any supported version) Cloud or Server |
| Azure DevOps Tasks to Jira Tasks | Username + API Token  | Create / Read / Update issues; Access to target projects | Jira Software or Jira Service Management, Version 7.x or newer | Username + PAT                | Read / Write work items; Access to target project | Azure DevOps (any supported version) Cloud or Server |
| Jira Bugs to Azure DevOps Bugs   | Username + API Token  | Create / Read / Update issues; Access to target projects | Jira Software, Version 7.x or newer                            | Username + PAT                | Read / Write work items; Access to target project | Azure DevOps (any supported version)                 |

***

### Setup

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

{% stepper %}
{% step %}
Log in to your ZigiOps instance
{% endstep %}

{% step %}
Navigate to ZigiOps - Configurator
{% endstep %}

{% step %}
Load the desired Jira and Azure DevOps integration template
{% endstep %}

{% step %}
Select the corresponding Integrated Systems (Jira and Azure DevOps)
{% endstep %}

{% step %}
Click **Save** to continue
{% endstep %}

{% step %}
Enable the integration using the slider button located in the middle section of the screen
{% endstep %}
{% endstepper %}

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 Azure DevOps integration scenarios. Mappings can be customized per use case.

**Example: Jira Task to Azure DevOps Task**

| Jira field  | Azure DevOps field | Advanced Field Mapping Example                   |
| ----------- | ------------------ | ------------------------------------------------ |
| Summary     | Title              | -                                                |
| Description | Description        | -                                                |
| Priority    | Priority           | -                                                |
| Status      | State              | To Do - New, In Progress - Active, Done - Closed |
| Assignee    | Assigned To        | -                                                |
| Comments    | Comments           | -                                                |
| Attachments | Attachments        | -                                                |

**Example: Azure DevOps Task to Jira Task**

| Azure DevOps field | Jira field  | Advanced Field Mapping Example                   |
| ------------------ | ----------- | ------------------------------------------------ |
| Title              | Summary     | -                                                |
| Description        | Description | -                                                |
| Priority           | Priority    | -                                                |
| State              | Status      | New - To Do, Active - In Progress, Closed - Done |
| Assigned To        | Assignee    | -                                                |
| Comments           | Comments    | -                                                |
| Attachments        | Attachments | -                                                |

***

### 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?</summary>

Yes. Filters and conditions allow you to scope synchronization by project, 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>Does ZigiOps store my Jira or Azure DevOps data?</summary>

No. ZigiOps does not permanently store transferred business data.

</details>

***

### Related resources

* [How to connect Jira to ZigiOps](#)
* [How to connect Azure DevOps to ZigiOps](#)
* [Data mapping fundamentals](#)
* [Jira and Azure DevOps 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-azure-devops-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.