This documentation relates to an earlier version of Crucible.
View

Unknown macro: {spacejump}

or visit the current documentation home.

Comments in Crucible can be used to flag a defect in the code under review.

to do this, simply tick the 'Defect' box when adding a comment and select a category from the drop-down list.


Screenshot: Defects

You may want to mark comments as defects to associate defect classifications, or simply to highlight to the author or moderator that the issue you raised in your comment requires attention.

(info) Crucible intentionally does not mandate how defects are to be used. The Crucible administrator can customise the defect classifications.

(info) You can only use the defect classifications on comments that are not a reply to an existing comment.

5 Comments

  1. Anonymous

    Apr 02, 2012

    I'm not sure if I understand how defect works.  Once a defect is flagged, can the author unflag it after making the changes suggested?  Does it stop the review from being completed?  Or is it just informational?   

    One of the reviewers here said it feels weird to mark a review completed when it has defects on it.  His question was if a defect is resolved, how do you unflag it?

  2. Anonymous

    Apr 05, 2012

    that's the same question i have.  the only way to resolve it is to 'Edit' and unmark and 'Defect' checkbox by the reviewer. could someone please answer?

  3. Anonymous

    Jun 08, 2012

    Are defects automatically turned into JIRA tickets? I can't seem to find a way to do that... but the Crucible docs say that Crucible can create tickets in JIRA...???

  4. Mark Reis

    Jun 13, 2012

    I have the same question about how to "dismiss" defects or marked them as fixed (other than using JIRA). 

    To answer the question about how to turn on JIRA tickets in Crucible, go to the Admin page of Crucible and under Global Settings you'll find Application Links. Set up a link to JIRA if you have not. Then click Configure the JIRA Settings and you'll see a "Subtask Setings" section at the bottom of that page. You can then type in the Subtask Type ID that you'd like to create when there is a Defect, the Subtask Action ID, and the JIRA Resolution type you would like when the user clicks "Resolve". Then after you create a Defect in a review, you'll see a link to create a JIRA item.

  5. Anonymous

    Jun 18, 2012

    There should be a way for someone other than a reviewer (like the person who created the code review) to "unmark" a defect either when new code is uploaded or if it was falsely set as a defect.



Log a request with our support team.



Raise an issue for our developers.



See answers from the community.



Blog and update our documentation.

Except where otherwise noted, content in this space is licensed under a Creative Commons Attribution 2.5 Australia License.