Bitbucket commits starting with Jira ticket number not displaying on Jira ticket

[DHSV]

When I used Jira and Bitbucket in 2017, professionally as well, pushing a commit to Bitbucket with a message starting like "JRA-34", the branch and commits would show up in the Jira ticket. Since Jira's "new and improved" project version, they don't.

This is supremely frustrating, as the only apparent way to get them to show up is to create a branch from the ticket to Bitbucket, which automatically generates a ridiculous branch name that includes the ticket title, when the ticket title in the branch name is unnecessary (since ticket numbers are unique), overly-long (which can be hard to read, or push content aside in apps like SourceTree), and the ticket title can change based on it becoming more clear what the issue is about (which helps with search in Jira).

How it behaved in 2017 was sensible and easy and simple; how it behaves now is difficult and overly-complex. I don't understand why this change happened. I'm not seeing how to get branch commits to attach to the tickets when the branch is named after the ticket number and each commit starts with the ticket number.

[seanaty]

@DHSV I think it still does this, but you need to make sure that your Jira site is linked to your Bitbucket account. Just making a commit with an issue key will not create this link.

Once the accounts are linked, committing changes should result in the branch data appearing on Jira (and the Jira data appearing in links on Bitbucket)

Have you tried following these steps? https://support.atlassian.com/bitbucket-cloud/docs/connect-bitbucket-cloud-to-jira-software-cloud/

[DHSV]

It is linked. We've already checked that multiple times over the years. We originally linked it. 

I did notice that some tickets are showing the branches and commits, though I don't know what triggered them.

It seems random at this point.