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?