reference: http://extranet.atlassian.com/x/_QPFYw

• When the assignee initiates the "Request Review" action, a review would automatically created in Crucible, including all change sets associated to the issue and not previously included in another Review associated with this issue.
• The workflow transition would allow the assignee to enter a comment, which would be included both in the Review's statement-of-purpose and as a JIRA comment.
• The Review statement-of-purpose would also include the commit messages of each changeset as well as a link to the issue.
• The assignee would be allowed to select additional reviewers.
• The assignee would be set as the moderator.
• When the review is completed by the moderator, Crucible would ask the moderator whether the JIRA issue should be resolved or reopened and allow the moderator to add a comment.
• Crucible automatically makes the right workflow transition and appends the comment in JIRA.
• Issues cannot be resolved while there are outstanding reviews. If you attempt to do so, it should remind you to close the outstanding reviews.

All of this should be triggerable as part of a workflow from a svn commit message too (ie if user says #close AOD-123 and the workflow says that the next step is Request Review, it puts the issue into Request Review).