What makes a Deployment appear in Jira for a specific issue?

[James Cheese]

We've recently been rolling out Bitbucket Pipelines for our builds. That's all going pretty well now (after some heavy scripting...) and on the Bitbucket side of things, builds are showing up properly attached to PRs, and then we've got branches set up for our test environments (etc) to merge onto, which will automatically deploy to the correct environment.

The issue we're hitting at the moment is getting Jira to reliably update with deployment information. On the Bitbucket side, when we run a test deployment, that deployment seems to correctly pick up the issues that should be attached to it:

But in Jira, the deployment only seems to attach to one ticket (possibly because it's the one labelled in the merge commit onto the test branch?

This is also reflected when viewing the individual issues - in this example, for NN-2223, there's a Release section in the sidebar , but NN-2296 has no such entry.

What controls how cases get attached in Jira? Does it ignore the information that Bitbucket has and just parse the commit messages? Is there anything we can do to work around this?

[Walter Buggenhout]

Hi @James Cheese ,

In short:

• Enable the deployments feature in Jira
• Configure a pipeline in your deployment tool
• Connect your deployment tool to your Jira site
• Link your development work to Jira using issue keys
• Make sure a deployment has run

Your question is - I assume - mainly about the last step.Jira will only show deployment information if a deployment has run on at least one linked branch, commit, or pull request. A deployment to an environment, such as production or testing, is linked if a commit associated with the deploy contains the issue key in its commit message.

You can read up on more details for each step in this support article 

Hope this helps!

[James Cheese]

Hi @Walter Buggenhout - thanks for the prompt response!

That's exactly the part I was asking about. Specifically I'm trying to find out if it's supposed to be just the last commit (ie: the precise commit the deployment was fired against) that is linked in Jira.

In the example I've posted screenshots for, Bitbucket shows 3 commits associated with the deployment - each of these is a merge commit that includes the issue tag in the body:

And as per the screenshots in the question above, it's correctly associated in the Issues tab in Bitbucket, but only one of the two cases is associated within Jira.

Based on the description in your link that a deployment "is linked if a commit associated with the deploy contains the issue key in its commit message", I assume this should count all commits in the deployment, and so should include both cases? Happy to raise a bug/support ticket about it - just want to make sure it's not expected behavior first!