Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Next challenges

Recent achievements

  • Global
  • Personal


  • Give kudos
  • Received
  • Given


  • Global

Trophy case

Kudos (beta program)

Kudos logo

You've been invited into the Kudos (beta program) private group. Chat with others in the program, or give feedback to Atlassian.

View group

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

Can an iterative pre-commit review be used even after post-commit?

Currently, for large code quantity of code changes, we are doing pre-commit reviews.  However, there is no guaranty that the final patch that was reviewed is the code that is checked into the repository.   Can an iterative pre-commit review become a post commit review?  Or will another review have to be opened after the code is committed?  If not, is there a way to link a pre and post commit review so the entire review/code change process is documented?

2 answers

1 accepted

0 votes
Answer accepted

To link your review with another, open Edit Details dialog and go to "Linked Review" field.

image2016-9-1 8:8:59.png

Thank you for your answer.  This seems to be the best option as with out JIRA, it doesn't look like a review can be opened as a pre commit and continue to be reviewed after post commit (without having to open up another review).  My issue is that many times, the last patch I reviewed, will include tweaks I did not approve before being checked in.  


Let me ask you a question: why do you use pre-commit reviews? From description of your problem I have an impression that you should rather try to setup a branch workflow process in your team, i.e. to develop feature on a branch, perform review on a branch and next merge changes to master/trunk. This way you'll be able to easily spot non-approved commits. 

Yes, you are correct regarding review branch. Unfortunately we didn't start out working on a review branch and our teams offshore created the the pre commit reviews (there are many)  already.  If the functionality in Crucible was available to track a pre commit review through post commit, then I was going to take advantage of it.  We will start the review branch development next load. 

Thank you!


1 vote

is there a way to link a pre and post commit review so the entire review/code change process is documented?

You can link a review to a JIRA issue. Also many reviews can point to the same issue. In JIRA, on the issue view page, in the "Development" panel you will see a link to related reviews.

We only purchased Crucible and Fisheye.  Besides, using JIRA, are there currently other ways? Thank you for your response.

It depends on your needs, actually. For instance, you can add a global comment to a review and put a key(s) of the related review(s) in it. You can also use the "Activity" tab to see if all comments have a review(s) associated with it. You can also use the Release Report plugin to check content between two arbitrary changesets.

Suggest an answer

Log in or Sign up to answer
Community showcase
Published in Data Center

Introducing Data Center Community licenses

I'm Alison Huselid, Head of Product for Data Center at Atlassian. As we shared in our last post, we’ve been working on a solution for those of you who work for charitable non-profit organizations tha...

699 views 10 40
Read article

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you