Preferred way of working when commiting new changesets to a ticket when a review is done on the existing changesets of that ticket

Gert Willems July 9, 2014

We have Fisheye/Crucible and Jira integraded through an application link.

When we do a review on a ticket, this usually evolves in additional changesets being committed to that ticket. To include these changesets to the review, we need to do 'Add content' in Crucible on the review and select the new changesets.

Is this the intended way of working or is there a way to 'rescan' the changesets of a ticket for inclusion in a review?

(abandoning the existing review and creating a new one is not really an option as that would force the reviewers the re-enter their comments in the new review),

kind regards

1 answer

1 accepted

1 vote
Answer accepted
gustavo_refosco
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
July 11, 2014

Hi Gert,

I believe what you're looking for can be achieved by using the Smart Commits to add your commit directly to an existing review, as exposed in the Smart Commits document. This would be achieved by adding "+review <review-key>" to your commit message.

Suggest an answer

Log in or Sign up to answer