This commit is not reachable from any branch or tag in this repository. It may be from a fork outsid

[Rohan Bag]

we have a Jira bug and have made a commit with the Jira ID in a branch.

now I cherry-picked the commit to the main branch and deleted the old branch from remote

in Jira I see two commits with different hashes and the same commit(same content and message) 

when I click on commits from Jira one commit is in a branch but the other gives the following output 

This commit is not reachable from any branch or tag in this repository. It may be from a fork outside of this repository.

I would ideally like to see only one commit id in jira.

[Viraj Bhosle]

facing same issue

[Andy Heinzer]

Hi @Rohan Bag 

I created a support ticket on your behalf over in https://getsupport.atlassian.com/servicedesk/customer/portal/23/JST-945971

If you could, please provide some more details about which specific issue you see this problem on.  Also, if you are willing to, you can grant data access to our support team.  That part isn't required to troubleshoot this, but it tends to make it a bit easier for our support to see the specific problem first hand.

[Viraj Bhosle]

Facing same issue  @Andy Heinzer what was the solution? Can't see your ticket. 
We had a heap dump in very old branch. I deleted the pull request and then the branch from bitbucket UI. But commit remained dangling now. 

Commit is accessible from bitbucket ui and shows "This commit is not reachable from any branch or tag in this repository. It may be from a fork outside of this repository."

We then tried to create a branch from local copy of that old branch and push it. It got pushed. Now commit was not dangling anymore. 

then used BFG repo cleaner. It removed the large files from the branch. But now again bitbucket shows dangling commit with same error message, commit is not reachable. Spent 2 days on it so far no luck

[Andy Heinzer]

Hi @Viraj Bhosle 

Unfortunately, I don't believe there has been a clear solution here.   The problem here stems back to the manner in which Jira identifies which commits to display.  Jira is looking for the issue key of the Jira issue as the sole means for determining which branches, commits, pull requests to include upon the JIra development panel.

We have a feature request over in https://jira.atlassian.com/browse/JSWCLOUD-22318 seeking to have some other means to hide specific dev info from appearing within Jira.  I would encourage you to vote on that ticket and if you like leave comment there about how this affects your team.

Thanks

Andy

[Viraj Bhosle]

Ohh I have put question in wrong forum. My issue is purely bitbucket related not jira.