Crucible’s pre-commit review (i.e. reviewing changes not yet in your SCM) hasn’t always been that flash. At least until now.
In Crucible 2.2, we introduced a small, but significant, feature that makes pre-commit reviewing using patches way better. The feature was cryptically called “patch anchoring” in the release notes, so I thought it might be worth highlighting why this is a good thing. Basically, patch anchoring lets you specify which revision in your SCM is the “from” revision in your patch. In fact Crucible guesses it, and you can easily change it if its wrong.
By far the most useful thing this anchoring enables is full context diffs. That is, upload a standard patch (usually with 0 or 3 lines of context) and look at the diff with as many context lines as you want.

Left: A normal patch diff with 3 lines of context. Right: The same patch with full context

You can also view the full source as it will look after the patch has been applied even though patches only include the changes.

So this is a pretty pointless screenshot, but I’ve uploaded the sucker into this mt pita so enjoy!

Anchoring also gives you links to the Fisheye history and the ability to add other commits.
So as I said at the beginning this is a small feature. However, if your code review process requires pre-commit code reviews this is really going to make your life better. For the rest of us, it will make reviewing the occasional contributed patch a lot easier.
Note: This feature requires Fisheye, so it only works with Fisheye supported version control systems, which is now quite a few (Subversion, CVS, Perforce, Git & ClearCase).

Better pre-commit code reviews with patches