Skip to content

Latest commit

 

History

History
80 lines (46 loc) · 4.67 KB

tutorial.md

File metadata and controls

80 lines (46 loc) · 4.67 KB

Integrate with Jira Issue tracking

Teams often use multiple tools and services in their DevOps workflows. Azure DevOps believes in giving you, the users a choice of tool for all parts of the pipeline without impacting the bidirectional flow of information for E2E traceability.

Azure Pipelines and Atlassian partner together to bring an integration of Azure Pipelines with Jira software cloud. The integration adds links to Jira issues as work items deployed with the pipeline and enables you to view deployment details from Pipelines directly in Jira issues. You can now automatically include Jira issues in release notes, and you can completely track delivery of issues without leaving Jira.

WIT view in release releases in Jira

This tutorial provides a step by step guide for connecting Azure Pipelines with Jira software cloud and enabling communication between the services.

Prerequisites

You must be a Jira site adminstrator to install the integration.

GitHub for Jira application must be installed and connected to the correct accoutns and repositories in GitHub. You would need to add Jira issue keys to the commit or pull request messages for the information to be available in Azure Pipelines.

This tutorial assumes the team is using the following tools in their DevOps pipeline.

DevOps pipeline

Connecting Azure Pipelines and Jira Cloud

The first step to get started is to connect the two services together.

  1. Install the Azure Pipelines for Jira application from the Atlassian marketplace
  2. On the post installation page, start adding your Azure DevOps organization and complete the wizard. Add organization
  3. On successful completion, the organization would be listed for the application. Configured organizations

Configuring the release pipeline

The next step is to inform the release pipeline to interact with Jira cloud for issue tracking.

  1. In the release pipeline configured for continuous delivery of the project, enable “report deployment status to Jira” and provide a mapping of the stages to deployment type.

    Edit release pipeline

Get it working

Let us see it in action E2E.

  1. Make a commit in GitHub including the Jira issue key in the commit message. In case you are using pull requests, the issue key can be included in the pull request title as well. This ensures the commit, branch and pull request are linked with the issue and shown in the development panel.

    commit

  2. It would automatically trigger the CI/CD pipeline in Azure Pipelines.

    triggered release

  3. View the work items included in this deployment. Jira issues would be listed automatically.

    View WIT in deployment

  4. In the Jira issue, the releases section informs the highest environment the issue has been deployed to.

    releases section

  5. You can also see latest deployments to each environment for the issue.

    release details

FAQs

  • How do I add another Jira cloud instance to my Azure DevOps account? The integration is triggered from Jira software cloud only. To add another instance to your Azure DevOps account, install the app on the instance and add the Azure DevOps organization to it.

  • Can I add multiple Azure DevOps organizations to a Jira cloud instance? Yes. You can configure the integration for multiple Azure DevOps organization from the manage application page in Jira cloud.

  • How do I add another project in a pre-configured organization to the integration? Use the add organization button to add additional projects in organizations already configured for the integration.

  • The information flow is not working. What should I do? Try by removing the organization from Jira cloud and reconfiguring the integration. You may need to update the release pipeline as well. Data for existing releases would not be impacted by this.

  • Can I also see builds performed by Azure Pipelines in Jira? The integration currently supports traceability for deployments (releases) only. Viewing build information in Jira is not supported.