# DevOps to DevOps Integration

Whether your teams work across Jira and Azure DevOps, GitHub and Jira, Bitbucket and Jira, or Jenkins and any issue tracker, ZigiOps enables real-time, bi-directional data exchange between any two DevOps platforms.

### What DevOps Systems Can I Connect?

ZigiOps supports 60+ enterprise systems. Any two DevOps tools with accessible APIs can be connected, including:

* Jira (Software and Service Management)
* Azure DevOps
* GitHub
* Bitbucket

| Source DevOps tool (examples) | Target DevOps tool (examples) | Typical Scenarios                                                                 |
| ----------------------------- | ----------------------------- | --------------------------------------------------------------------------------- |
| Jira                          | Azure DevOps                  | Sync Jira issues and Azure DevOps work items across product and engineering teams |
| Jira                          | GitHub                        | Create GitHub issues from Jira; sync labels, status, and comments back            |
| Azure DevOps                  | Jira                          | Forward Azure DevOps work items to Jira for cross-team visibility                 |
| Bitbucket                     | Jira                          | Link Bitbucket commits and issues to Jira tickets                                 |
| Jenkins                       | Jira                          | Create Jira issues from Jenkins build failures automatically                      |
| **Any DevOps tool**           | **Any DevOps tool**           | **Any entity, any field, any direction - configurable via ZigiOps**               |

> **Note:** ZigiOps can integrate with any DevOps system that exposes a REST API, even if it is not in the pre-built template library.

### What Data Can Be Synchronized?

ZigiOps supports synchronization of all standard and custom fields, status transitions, comments, attachments, labels, and build metadata between DevOps tools. Each field can be mapped independently per direction.

| Entity type             | Direction       | Examples                              | Common fields synchronized                                                          |
| ----------------------- | --------------- | ------------------------------------- | ----------------------------------------------------------------------------------- |
| Tasks / Work Items      | Bi-directional  | Jira Issue - Azure DevOps Work Item   | Title/Summary, Description, Priority, Status/State, Assignee, Comments, Attachments |
| Bugs / Defects          | Bi-directional  | Jira Bug - GitHub Issue               | Title, Description, Severity, Status, Assignee, Labels, Comments                    |
| Build / Pipeline events | CI - Tracking   | Jenkins Build - Jira Issue            | Build ID, Status, Result, Branch, Triggered by                                      |
| Custom work item types  | Both directions | Any DevOps entity - Any DevOps entity | All standard and custom fields supported                                            |

### How Does the DevOps to DevOps Integration Work?

ZigiOps acts as a secure integration layer between two DevOps systems, using their native APIs to read and write data.

* No scripting or custom development required
* All configuration is done through the ZigiOps UI
* Supports polling-based and event-driven (webhook) synchronization
* Start from a pre-built template or build a custom integration from scratch
* Apply field mappings, transformations, conditions, and filters per use case
* Does not permanently store transferred business data

### Setup

Follow the steps below to enable a DevOps to DevOps integration using ZigiOps.

1. Log in to your ZigiOps instance.
2. Navigate to **ZigiOps - Configurator**.
3. Load the desired integration template (or create a new one from scratch).
4. Select the corresponding **Integrated Systems**.
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.

### Frequently Asked Questions (FAQ)

<details>

<summary>Do I need coding or API skills to set up a custom integration?</summary>

No. All configuration is handled through the ZigiOps UI. No scripting or API expertise is required.

</details>

<details>

<summary>Can I integrate systems that do not appear in the pre-built template library?</summary>

Yes. ZigiOps allows you to create integrations from scratch for any system with an accessible API.

</details>

<details>

<summary>Is bi-directional synchronization supported?</summary>

Yes. All integration types support bi-directional data flow, configurable per field.

</details>

<details>

<summary>How does ZigiOps prevent update loops?</summary>

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

</details>

<details>

<summary>Can I apply conditions and filters to control which records are synchronized?</summary>

Yes. Conditions, filters, and transformations can be applied at the field, record, or workflow level.

</details>

<details>

<summary>Does ZigiOps store transferred business data?</summary>

No. ZigiOps does not permanently store transferred business data.

</details>


---

# 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/devops-to-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.