When I reset a commit in Bitbucket to an earlier commit, why isn't it reflected in Fisheye reviews?

[John Bottiger]

I was instructed to pull from the main development branch of a repo into my feature branch.  The feature branch is already in review under Fisheye/Crucible.  After finding merge conflicts, I committed the resolved merge conflicts and pushed the changes into Bitbucket to my feature branch there.  At the same time, my Fisheye/Crucible review updates to reflect the latest changes.  However, I performed a git reset to go back to an earlier commit, performed a "forced" push into my feature branch in Bitbucket, but that change did not get reflected in Fisheye/Crucible.  Why is that?

[Martin Runge]

Hi @John Bottiger

This issue, I guess, happens because Fisheye indexes repositories linearly by listening for new commit events, but it does not automatically detect when the Git history is rewritten via a force push. When you perform a git reset and a force push, the old commits still exist in Fisheye's database, and it does not inherently know it needs to remove them or update the active Crucible review.

To resolve this and realign your review, you must prompt Fisheye to reindex and detect your branch's current state. You can do this by manually re-indexing the repository via the administration panel at Administration > Repositories, then choosing the o repository option to Rescan or Re-index.