Issue: We have a review where most of the changes are due to re-organization of the files: either files moved to a directory or renamed. And then a few edits. Those renamed files don't show any diff in crucible, they only show the end result of the file, as if it is a brand new added. If the file is not renamed nor moved, then the diffs are shown correctly.
Related to this, git log has a --follow option, that shows history of a file before it was renamed.
Question: Is there a similar option with fisheye so that it can follow the file's history before it was renamed?
You can change the way Crucible detects renames in your Git repository.
For this go to
Crucible Administration > Repositories, open your repository configuration and go to SCM Details. Here you can edit the Rename Detection option. Changing it to detailed, for instance, will make Crucible to detect the rename as a change - it will still show the old name as a deletion, but you could just remove it from the review created, as when creating a review on top of this commit it will add both the renamed (changed) file as well as the deleted one.
Please notice that when changing this setting and saving it Crucible will prompt you for a restart on the repository. This will not be enough to make files already indexed to be shown as changes - if you want them to be shown this way, a full re-index will be required (
repo settings > Maintenance > Re-clone and Re-index).
You can check further on this and other Git options at https://confluence.atlassian.com/display/FISHEYE/Git.
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
We're bringing product updates and pro tips on teamwork to ten cities around the world.Save your spot