What links a JIRA issue to Bitbucket commits/PRs

[Edward Basiliere]

Hello,

We are using the server versions of both JIRA and Bitbucket. When I view JIRA project releases I can view issues belonging to that release. The Development column shows commits and the merge status of pull requestsl linking to those tickets. 

I see commits linked from having the JIRA issue ID in the commit message. What else creates this link? Branches with a JIRA issue ID in the name? Anything else?

Thanks!

[Mikael Sandberg · Accepted solution]

JIRA issues are linked when you mention the JIRA key in Bitbucket, either in the branch name, as part of the description or comment in a pull request or as part of the commit comment (as you have seen). 

Here is some more information about the integration, https://confluence.atlassian.com/bitbucketserver/jira-integration-776639874.html

[Edward Basiliere]

Perfect. Thank you!

[Edward Basiliere]

Do user forks not apply?

I committed to a user repo under my account, which displayed the commit fine in the Development area in the JIRA issue.

When I attempted the same in a forked repo under my account, the commit did not display in the JIRA issue.

I also tested with a fork that is under a project, not a user account, and that displays fine.

Thanks.

[Ben Taylor]

I've run into this just now, I find that issues are linked in the Bitbucket PR if I mention the JIRA ticket in the git branch name or in the git commit message, but they if I mention them in the PR description or in a comment then the text is hyperlinked but the ticket number does not appear at the top as a linked ticket. This doesn't seem to be the expected behaviour, going by the answer above?

[Stanislav German-Evtushenko]

Automatic linking with a JIRA ticket by mentioning the key in a commit doesn't work for me either (though it used to work in the hosted Bitbucket). Has anything changed since then?