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

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:

In Azure DevOps, they are called Related Work:

Setting Up Dependencies

Jira - Jira Integration:

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.

1. 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.

If you are dealing with legacy tasks that have not been migrated, anticipate potential errors by migrating them first, so they synchronize correctly.

Jira - Azure DevOps Integration:

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 and Reference guide for link types.

1. 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.

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.

Conclusion

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 or schedule a demo with our team. We're happy to help you build the integration that fits your workflow.