Defining your workflow

On this page

Still need help?

The Atlassian Community is here for you.

Ask the community

This page provides brief outlines of three different ways that a development team could use Crucible for code reviews:

For a detailed example of how to perform Crucible reviews with two participants, see The Crucible workflow.

Lightweight code commenting with Crucible (individual)

  1. Author commits new work.
  2. Author creates the review, and adds comments using the easy web interface.
  3. Author summarizes and closes the review, saving the code comments in Crucible (and not in the code repository).

    Lightweight code commenting

 

One-to-many reviews without a moderator (Agile team)

  1. Author creates the review.
  2. Author invites reviewers to take part in the review.
  3. Reviewers make comments on the code.
  4. Author responds to reviewer comments, making follow-up comments as necessary.
  5. Reviewers complete their reviews.
  6. Author summarizes and closes the review.

    one-to-one-review

 

Formal group reviews (CMM team)

  1. Author creates the review.
  2. Moderator invites reviewers to take part in the review.
  3. Reviewers make comments on the code.
  4. Author responds to reviewer comments.
  5. Follow-up comments are made if necessary.
  6. Each discussion point is settled by the Moderator.
  7. Moderator summarizes and closes the review.

    Moderated review

Last modified on Nov 28, 2018

Was this helpful?

Yes
No
Provide feedback about this article
Powered by Confluence and Scroll Viewport.