Bitbucket branch is not linking to Jira issue

[Bárbara Silva]

I just noticed that some branches on my Bitbucket repos are not linked to their Jira issues, even though they have the issue key in their names, for example:

bugfix/2023-1-15-JIR-123-description

Other branches, like "feature/JIR-123-description" and "feature/master-JIR-123-description", are correctly linked.

I've checked the article below and it just mentions that the branch should have the issue key in its name: 

https://support.atlassian.com/jira-software-cloud/docs/reference-issues-in-your-development-work/

Is there some specific rule for branch naming when it comes to Jira linking? For example, it seems this is not working as expected when the issue key comes after some numbers followed by a hyphen.

Thanks!

[Becky]

Hi Barbara,

We have gone through similar problems with FishEye integrated with Jira.

I am not sure if the following solution can be applied to Bitbucket as well, but I think it's probably worth mentioning:

1. Make sure your repository is created and indexed

2.  There should not be any special characters before the issue key.

• • For example, “Message - SSD-2 Testing commit” is an example of a bad practice. The dash before issue key “SSD-2” will result in the commit not showing in the Development Panel.
  • Reference: This is a known bug reported to Atlassian Fisheye. View the reported issue here: JSWSERVER-14893