> For the complete documentation index, see [llms.txt](https://docs.getint.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.getint.io/guides/integration-synchronization/jira-azure-devops-integration/syncing-dependencies-between-jira-and-azure-devops-using-getint.md).

# Syncing Dependencies between Jira and Azure DevOps using Getint

## Linking Work Items for Getint Integration

Dependencies allow teams to establish relationships between work items, such as blocked tasks, predecessors, successors, or related work. Synchronizing these relationships is essential when multiple teams collaborate across Jira and Azure DevOps.

Because Jira and Azure DevOps use different dependency models, synchronizing these relationships manually can be difficult. Getint acts as an intermediary, translating dependency information between both systems so that linked work remains connected regardless of the platform being used.

This article explains how to configure dependency synchronization between Jira and Azure DevOps using Getint.

### Understanding Dependencies <a href="#understanding-dependencies" id="understanding-dependencies"></a>

Azure DevOps stores dependencies as **Related Work**, whereas Jira stores dependencies as **Linked Items**.

Depending on your process template, Azure DevOps and Jira may provide:

* System-defined links
* Process-defined links
* User-defined links

Common examples include:

* Parent / Child
* Predecessor / Successor
* Related

Before configuring dependencies in Getint, make sure the desired Work Item Link type exists in both Azure DevOps and Jira.

#### In Jira, dependencies are called Linked Work Items:

<figure><img src="/files/2k3iiFjycKuqVTCRuW0S" alt=""><figcaption></figcaption></figure>

#### In Azure DevOps, they are called Related Work:

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

### Setting Up Dependencies

#### Jira - Jira Integration: <a href="#jira-jira-integration" id="jira-jira-integration"></a>

1. **Configure Dependencies in Jira:**
   * Jira comes ready with the linking issues option enabled. Verify your system setup for any adjustments, and if needed [Configure Dependencies in Jira for your plan](https://support.atlassian.com/jira-software-cloud/docs/configure-dependencies-in-jira-for-advanced-roadmaps/).

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

2. **Syncing Jira-Jira Dependencies with Getint:**
   * Open your Getint instance, select the integration tab, and choose the integration.
   * Access the Dependencies section to configure settings.
   * Match project dependencies on both ends and ensure corresponding links for accurate mirroring.
   * Click **Apply** and then **Save** to enact changes. The next synchronization will update dependencies for new tasks based on matched fields.

{% embed url="<https://www.loom.com/share/9b263c72697e491a9d83c31034978dfe>" %}

{% hint style="info" %}
If you are dealing with legacy tasks that have not been migrated, anticipate potential errors by migrating them first, so they synchronize correctly.
{% endhint %}

#### **Jira - Azure DevOps Integration:** <a href="#jira-azure-devops-integration" id="jira-azure-devops-integration"></a>

1. **Understanding Work Item Links in Azure DevOps:**
   * Azure DevOps offers **Related Work** options for linking tasks, featuring system-defined, process-defined, or user-defined link types. To learn more about how to create a Work link in DevOps, see the guides: [Link work items to objects](https://learn.microsoft.com/en-us/azure/devops/boards/backlogs/add-link?view=azure-devops) and [Reference guide for link types](https://learn.microsoft.com/en-us/azure/devops/boards/queries/link-type-reference?view=azure-devops\&source=recommendations).

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

2. **Syncing Jira-DevOps Dependencies with Getint:**

* Open the integration tab and choose the integration.
* Navigate to Dependencies to configure settings.
* Align Jira dependencies with their Azure DevOps-related work items links.
* Click **Apply** and then **Save** to implement changes. The next sync will seamlessly integrate the new dependencies.
* Getint will then update tasks with the corresponding Work link based on matched fields, applying to new and migrated items. Ensure non-migrated tasks have the necessary link field.

{% embed url="<https://www.loom.com/share/2003fc8e598640e989efd31c759cbf07>" %}

{% hint style="warning" %}
When mapping fields, do not select the **Linked Issues** option in dropdowns. Use the Dependency box for creating dependencies between platforms.

Links will be established only if both items intended to be linked within the app have already been synchronized by Getint. Otherwise, they will be skipped.
{% endhint %}

### Conclusion <a href="#conclusion" id="conclusion"></a>

By configuring dependency synchronization in Getint, you can keep relationships between work items consistent across Jira and Azure DevOps. This keeps blockers, predecessors, successors, and related tasks connected, helping teams collaborate more effectively while continuing to work in their preferred platforms.

If you encounter any issues or need assistance configuring dependencies, please visit our [Help Center](https://getint.io/help-center) or [schedule a demo](https://calendly.com/d/cpws-jb2-8xx/demo-call-all-team) with our team. We're happy to help you build the integration that fits your workflow.

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


---

# 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 dynamically by asking a question.

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

```
GET https://docs.getint.io/guides/integration-synchronization/jira-azure-devops-integration/syncing-dependencies-between-jira-and-azure-devops-using-getint.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.