Jira development lost link to bitbucket commits after merge

egiatrakis
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
April 18, 2024

In our Jira (cloud) project we have noticed that some issues, not all however, have lost their linking to their relevant bitbucket commits after the respective Pull Requests have been merged and the relevant branches deleted. 

So far, we have been unable to identify any particular test patterns that this behaviour is triggered by and as I mentioned it is not very consistent. It has happened to the majority of our software tasks but not all. And the ones that still have their commits linked do not, as far as we can see, have anything special about them.

I should clarify that in our team, we always refer to the Jira issue as part of any commit message therefore, it is not that the commits are only linked to their relevant Jira issue through their branch and the linking is lost after the branch is deleted as part of the pull request's completion. Another important fact about this investigation is that bitbucket sees the linked Jira issue in every commit normally. It is just Jira that cannot see the commits for some reason.

Any help, direction or suggestion would be highly appreciated. 

In the image below you can see an example of an issue where linking has persisted even after merge. This is what we want to have on every software task.

2024-04-18 10_42_48-.png

0 answers

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
PREMIUM
TAGS
AUG Leaders

Atlassian Community Events