• Community
  • Products
  • Jira
  • Questions
  • Preferred way of working when commiting new changesets to a ticket when a review is done on the existing changesets of that ticket

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

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
Accepted answer

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
Community showcase
Published Nov 27, 2018 in Portfolio for Jira

Introducing a new planning experience in Portfolio for Jira (Server/DC)

In the past, Portfolio for Jira required a high degree of detail–foresight that was unrealistic for many businesses to   have–in   order to produce a reliable long-term roadmap. We're tur...

2,789 views 18 22
Read article

Atlassian User Groups

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!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you