Azure Pipelines integration with Jira Software
Some teams prefer to have a choice of tools for configuring development pipelines, and that is most effective when the tools are integrated and users can retain context as they move between systems for details.
Jira Software is a development tool used by agile teams to plan, track, and manage software releases. Using Azure Pipelines, teams can configure CI/CD pipelines for applications of any language, deploying to any platform or any cloud.
This integration connects the two products, providing full tracking of how and when the value envisioned with an issue is delivered to end users. This enables teams to setup a tight development cycle from issue creation through release. Key development milestones like builds and deployments associated to a Jira issue can then be tracked from within Jira Software.
Associated Jira issues can also be viewed in releases in Azure Pipelines for a complete deployment history per environment.
Some teams like to use Jira Software for issue tracking, GitHub as a source repository and Azure Pipelines for CI/CD. Developers add Jira issue keys to the GitHub commits and Azure Pipelines automatically keeps track of the commits consumed and associated issues in each deployment.
By adding build and release information from Azure Pipelines to associated Jira issues, we complete a three-way linking of information. Teams can start from any of the three services (Jira Software, Azure DevOps and GitHub) and get complete visibility into planning, development and deployment. Product managers can understand whether the feature can be used by end customers, developers can track whether their commits have been deployed to production, and release managers can create release notes in a jiffy.
Get started by installing Azure Pipelines integration with Jira and connect Azure DevOps organizations with your Jira Software instance. You can connect multiple organizations with one instance and get data for all your teams and related projects. Learn more about setting up the integration in our documentation.