Azure DevOps For Jira
Two-way sync of work items, comments & attachments, plus branches, PRs, commits, builds & deployments in Jira. Works with Azure DevOps (SaaS and On-Premise).
Two-way sync of work items, comments & attachments, plus branches, PRs, commits, builds & deployments in Jira. Works with Azure DevOps (SaaS and On-Premise).


Work items, comments and attachments stay in sync in both directions, including images in comments, labels and tags, and people fields.

Every sync attempt is recorded with its direction, issue and work item, rule and outcome. Failures come with a readable reason, so admins know what to fix.

Browse and filter all linked issues and work items, spot orphaned links, and re-sync, reconnect or remove a link in one place.
Learn how you can connect Azure DevOps and Jira in this demo video.
Azure DevOps for Jira automatically links all development activity - branches, PRs, commits, builds, and deployments - to the corresponding Jira issues. Smart commits let developers transition issues from their commit messages. Two-way work item sync keeps work items, comments and attachments aligned in both tools without manual effort.
Enterprise engineering organizations in hybrid Microsoft + Atlassian environments. Engineering teams using Azure DevOps for CI/CD and code, while PMs, product managers, and leadership track work in Jira. Common in companies that adopted Azure DevOps for its Microsoft ecosystem integration but Jira for its project management strength.
When developers commit code, merge PRs, and deploy in Azure DevOps, Jira doesn't know. Project managers manually check Azure DevOps for deployment status. Nobody knows if a Jira ticket's feature branch has been merged. And when work has to live in both tools, someone ends up copying updates, comments and files back and forth by hand.
Azure DevOps for Jira automatically links all development activity - branches, PRs, commits, builds, and deployments - to the corresponding Jira issues. Smart commits let developers transition issues from their commit messages. Two-way work item sync keeps work items, comments and attachments aligned in both tools without manual effort.
Key Differentiators vs. Atlassian's Native Integration:
Our most requested feature is live. Work items, comments and attachments now stay in sync in both directions: change something in Jira and Azure DevOps updates, change it in Azure DevOps and Jira updates. No duplicates, no update loops.
Latest sync improvements:
Also new for development information:
See how it works and how to set it up in our announcement: Two-way sync between Jira and Azure DevOps is here, or go straight to the setup guide.
A financial services company with 200+ developers is migrating from on-premise Team Foundation Server (TFS) to Azure DevOps Cloud. During the 6-month transition, some teams are on TFS and others have already moved to cloud. All project tracking runs through Jira.
The challenge: During migration, development activity is split across two Azure DevOps environments. Jira has no visibility into either without manual updates. PMs cannot tell whether a feature branch exists, if a PR has been merged, or if a build succeeded - they have to ask the developer or check Azure DevOps directly.
How the integration helps:
The result: PMs have full development visibility in Jira regardless of which Azure DevOps environment a team uses. The migration proceeds without losing traceability between work items and code.
A SaaS company runs 6 development teams across a shared codebase. Each team owns a Jira project and uses Azure DevOps for CI/CD. The release manager coordinates monthly releases and needs to know which features are code-complete, which builds are green, and which deployments are staged.
The challenge: The release manager checks 6 Azure DevOps pipelines manually before each release. Build failures are discovered late because they are only visible in Azure DevOps, not in Jira where sprint planning happens. Deployment status is communicated through Slack messages that get lost in busy channels.
How the integration helps:
The result: Release coordination time drops by half. The release manager makes go/no-go decisions from Jira dashboards instead of switching between 6 Azure DevOps projects. Build failures are caught and addressed the same day.
A healthcare software company must maintain complete traceability between requirements, code changes, and deployments for regulatory compliance. Auditors need to see which code changes relate to which requirements, who approved them, and when they were deployed.
The challenge: Linking Jira requirements to Azure DevOps commits and deployments is done manually in spreadsheets. The process is error-prone, time-consuming, and always incomplete by the time an audit comes around.
How the integration helps:
The result: Audit preparation drops from weeks to hours. The compliance team pulls traceability reports directly from Jira instead of assembling them manually from multiple sources.
A product company acquired two startups. The parent company uses Azure DevOps and Jira. One startup used GitHub, the other used GitLab. All teams are now consolidating on Azure DevOps for CI/CD, but the migration will take a year.
The challenge: Developers waste time context-switching between Jira and Azure DevOps. They create a branch in Azure DevOps, then manually update the Jira issue. They merge a PR, then go back to Jira to transition the issue. Multiply this across 80 developers and hundreds of issues per sprint.
How the integration helps:
The result: Developers estimate they save 10-15 minutes per day on manual Jira updates. Sprint velocity improves because less time is spent on administrative overhead and more on actual coding.
Not sure if this is the right integration for your team? Read our detailed comparison guides:
We prioritize customer data privacy with GDPR-compliant data collection and processing.
Azure DevOps for Jira integrates Azure DevOps with Jira to display Azure DevOps commits, branches, pull requests, builds and deployments in Jira.
Azure DevOps for Jira supports Jira Cloud as well as Azure DevOps Cloud.
Jigit supports Jira Data Center.
To install, navigate to the Atlassian Marketplace, search for Azure DevOps for Jira, and follow the installation steps. Once installed, configure the app to link your Azure DevOps organization and projects with Jira.
To get started, install the app from the Atlassian Marketplace, configure the integration to connect your Azure DevOps organization with Jira, and follow the setup guide to map your work items. For more details, visit our Getting Started Guide.
Please note that Azure DevOps for Jira works only with Jira Software projects, as they support the development panel.
We use Personal Access Tokens (PAT) to connect Azure DevOps and Jira. OAuth is only utilized to create branches from Jira. Move Work Forward adheres to industry security best practices to safeguard your data, and we take this commitment seriously. You can review our Trust Report for more information.
If you're encountering synchronization issues, make sure to review the integration settings to confirm that your Azure DevOps and Jira projects are properly connected. Also, ensure that the Personal Access Token (PAT) is valid, has the required access permissions, and has not expired. You can also refer to the documentation for more information.
Yes, customer support is available through the app’s support team. Additionally, comprehensive documentation and help articles are provided to assist with setup and troubleshooting.
The pricing for Azure DevOps for Jira varies depending on the size of your Jira instance and the number of users. Detailed pricing information is available on the Atlassian Marketplace listing.
Atlassian Marketplace Partners don’t have the tools to manage licenses, so you need to reach out to Atlassian Support.