How to refresh fetched commits in JIRA?

[Borek Bernard]

We have a JIRA connected to our BitBucket-hosted Git repository and JIRA correctly fetches related commits to our issues. It works fine but the problem is this:

When a Git branch is rebased, the commits get new SHA1 hashes as they are technically new commits. JIRA fetches these new commits again but doesn't remove the previously fetched / indexed commits that no longer exist in the repo.

How to tell JIRA to refresh the commits? Should I just disabled and enable the DVCS connector?

[Harm Verhagen]

I found the solution to this problem.

You can do a "Full synchronisation" of the DVCS accounts. But its rather hidden in the UI.

I found the solution here:

https://confluence.atlassian.com/bitbucket/synchronize-an-account-371360175.html

System -> Applications -> DVCS accounts

There are sync buttons next to your repos.  These buttons do a 'soft' sync. (reload new commits).  however....

if you press SHIFT en then click the sync button, you get a pop-up where you can choose between a "Soft synchronisation"  or a "Full synchronisation"

[IT Red]

Did you solve the problem despite the answer below in any way?

[Tim Crall]

You should not be rebasing commits that have already been pushed to BitBucket.  Best practice is to rebase only local commits - otherwise you are rewriting already public history.  This will cause problems, as you've encountered.  It will also cause problems for any other developers trying to work on the rebased branch.

[Borek Bernard]

In our case, the code is initially developed in a feature branch, then rebased on top of master after which the feature branch is deleted. This does not cause any issues for us, except for JIRA where we see duplicate commits (even the non-existent ones). Is there a way to force repo reindex?

[IT Red]

Any news on this question? We have the exactly very annoying problem!

[Harm Verhagen]

Same problem here.  we like featured branched to be reviewed (pull request in bitbucket), but rebased before eventually merging to master.  

This gives duplicate commits in jira.