This guide will show you how to quickly create a 2-way sync between Azure DevOps and Jira that turns work items into issues. When this guide is complete, you’ll know how to easily set up a no-code integration that keeps your software development work up-to-date in real-time. Whether you’re a Jira developer wanting visibility into Azure DevOps or a lead software developer streamlining cross-team work, Unito has you covered!
Here’s an example of our demo’s synced work item and issue:
The goal of this integration is two-fold:
- Create work items in Azure DevOps automatically whenever we manually generate specific issues in Jira, or vice versa.
- Maintain a real-time 2-way sync between issues and work items with automated updates whenever changes are made in either tool.
Why connect Azure DevOps with Jira?
The integration of these robust tools primarily leads to time, effort, and cost savings. If team members are unfamiliar with either Azure DevOps or Jira, then adapting to a new interface can prove challenging and lead to errors.
Integrating work items from Azure DevOps to Jira eliminates the need to search for specific projects, issues, or other tasks in each separate tool. Instead, these items will automatically populate, creating a distributed truth.
Facilitate software developer collaboration
Unito’s Azure DevOps Jira integration is particularly advantageous for project managers overseeing multiple teams concurrently, removing the need to constantly switch between tools.
Stay consistent from project to project or version to version with a united source of truth
A common challenge faced by teams utilizing various tools is sustaining a single source of truth for the latest project progress. In the realm of development teams, this relates to version control. By linking formerly isolated departments or collaborators, unity is achieved concerning project status, assignments, deadlines, and more.
Put an end to time-draining status meetings
Rather than endless status meetings, synchronizing issues with work items diminishes the necessity for constant updates, check-ins, or scheduled code reviews. This is achieved by granting appropriate team members access to synchronized data. Questions can be easily addressed through comments left in one tool, immediately visible in the other tool in real-time!
Watch Unito’s Azure DevOps Jira integration in action:
Before we connect Azure DevOps and Jira to Unito:
Adjust your organization settings in ADO
Be sure to adjust your Organization Settings in Azure DevOps before building your flow. Just make sure that Third-party application access via OAuth is turned on and that your project is public.
Configure Jira for Unito access
These steps are only necessary the first time you sync Jira with Unito.
- The Jira account connected to Unito must have administrator access with global permissions.
- You’ll need to set your Jira contact email visibility to anyone from your Jira profile page.
- Then, set up an application link in Jira so that your issues can sync to Trello cards.
Step 1. Connect Azure DevOps and Jira to Unito
Unito Standalone App:
Navigate to the Unito App and select +Create Flow.
- Login to your Jira account.
- Click on the Apps button in the top-right.
- Select Sync by Unito.
On the next screen, select Start Here to connect Azure DevOps and Jira. Choose the accounts and projects or folders you wish to sync.
When you’re ready, select Confirm.
Step 2. Set a flow direction between Azure DevOps and Jira
Here we can decide whether new Jira issues should create matching work items in Azure DevOps, vice versa, or both.
For our demo, we’ll be setting up a flow that creates new Jira issues based on work items in Azure DevOps. So whenever we manually create a new ADO work item, then Unito will automatically sync it to a newly created Jira issue.
Select Confirm when you’ve chosen a flow direction.
Step 3. Set rules to determine which work items to keep in sync
Rules allow us to decide whether or not to filter out specific issues or work items from syncing to our other tool. Select Add a new trigger to begin setting your rules. You can remove a trigger by selecting the bin icon on the right-hand side.
Step 4. Map fields between Azure DevOps work items and Jira issues
Next, you can decide which individual fields to sync between Azure DevOps and Jira, as well as how changes should appear in each tool. Most fields can be assigned their own directional flow so you can enjoy some customization here as needed.
But first, we have to pick between manual mapping and auto-mapping. Auto-mapping creates a template that can be modified, or you can start from scratch.
To add a new pair of fields, select + Add mapping, then Select a field in both Azure DevOps and Jira. Here is an example of our demo’s auto-mapped fields:
The above example shows you all the fields you need to map to match our demo’s use case. As you can see, summaries in Jira are synced to titles in Azure DevOps, description to description, and so on.
Choosing a flow direction for each field mapping determines whether or not changes in one tool will be reflected in the other.
Click Confirm when you’re satisfied with your field mappings to proceed.
Step 5. Save, close and launch your Azure DevOps, Jira integration
The only thing left to do is decide whether or not to sync historical work items. You can make this decision from your flow’s overview page, or edit your rules as mentioned above.
And that’s it! You’ve just completed a flow between Azure DevOps and Jira. Congratulations!
If you’ve followed the steps above, your flow will now:
- Create an issue in Jira based on a work item in Azure DevOps;
- Enable collaboration between Jira and Azure DevOps with a clear view on progress across tools
If you have any questions, don’t hesitate to reach out and let us know.
What’s next after connecting Azure DevOps and Jira with Unito?
Now that you’ve set up your integration between Jira and Azure DevOps, you can unify project management and improve cross-team visibility across tools with real time two way updates. You can also read more about Unito’s integrations for Jira and Azure DevOps to better understand their capabilities and limitations.