Problem

• Customers who store their source code in Bitbucket Cloud and use Azure DevOps Pipelines only for CI/CD (with no Azure Repos enabled) cannot see any Azure DevOps builds or deployments linked to Jira issues when using the Azure DevOps for Jira (Official) integration. In this setup, pipelines build and deploy Bitbucket repositories that contain Jira issue keys in commits and branch names, but because the integration only supports Azure DevOps repositories (Azure Repos) as the pipeline’s SCM source, it cannot detect those keys or associate Azure Pipelines activity with Jira issues. As a result, Jira shows Bitbucket development activity (commits, branches, pull requests), but no deployments from Azure Pipelines appear in the issue Development panel or the project Deployments view.

Suggestion

• Add support in Azure DevOps for Jira (Official) for pipelines that build and deploy Bitbucket-hosted repositories, so that Azure DevOps builds and deployments can be linked to Jira issues even when the underlying SCM is Bitbucket (and Azure Repos is not used).

Workaround

• Currently there is no direct workaround that keeps Bitbucket as SCM and Azure Pipelines as CI/CD while also showing Azure deployments in Jira.
  The only options today are:
  • Move or mirror the repository to Azure Repos and use Azure Pipelines against that Azure Repos repo, or
  • Use Bitbucket Pipelines (or another supported deployment integration) for Bitbucket-hosted code instead of Azure Pipelines.