Bitbucket Cloud Deployments Are Missing Under a Jira Issue Key

Summary

In certain cases, it becomes evident that deployments are not appearing under a Jira issue key. In an ideal scenario, when issue keys are explicitly mentioned within commit messages, Bitbucket Cloud creates a linkage between the commit and the Jira issue on Jira Cloud. Consequently, this results in the commit being reflected under the relevant Jira issue key, and any associated deployments will be displayed.

However, there are situations where, despite having Jira issue keys within the commit messages and successful pipeline runs, the deployments fail to appear under the respective Jira issue key. This discrepancy may be attributed to the Jira issue key within a commit message being unreachable from the commit on which the latest deployment is executed.

Solution

Example:

For instance, consider the following Git branch structure:

In this scenario, let's assume that production deployment with ID "1" is initiated from commit "B," and Jira issue key "JIRA-1" is issued to commit "Z" message. Subsequently, after commit "Z", commit "D" is made.

Now, if you intend to deploy to Production let's say, using commit "D," the deployment will encompass commits D and C, as they are reachable from commit D. However, commit B will be excluded, as it was previously deployed as part of deployment "1".

Commit Z, despite containing the JIRA-1 issue key, is not included in deployment 2, as it is not reachable from commit D. Consequently, this results in commit Z, associated with JIRA-1, deployment "2" not being displayed under "JIRA-1".

If you encounter similar issues and believe that the discussed use case is not related to your issue, please don't hesitate to reach out to our support team for further assistance.