Documentation for Crucible 3.0.x. Documentation for other versions is available too.

This page describes how to use the Reports tab in Crucible to see lists of people whose action is required on open reviews. These are known as 'blockers'.

On this page:

See also:

Viewing the Review Blockers report

To view a list of people who have open reviews assigned to them:

  1. Click the dropdown arrow next to the Reviews tab at the top of the page and select Reports.
  2. Click Review Blockers (under the 'Reports' sub-tab). 
    • Click a user's name to go to their 'Activity' screen.
    • Click a number in the 'To Complete' or 'To Summarize' column to go to a list of reviews for that user.

Screenshot: 'Review Blockers' Report

Viewing the JIRA Blockers report

The 'JIRA Blockers' report shows you a list of users whose action is required on open reviews, for a particular set of JIRA issues. The reviews must be explicitly linked to a JIRA issue or mention a JIRA issue key in the summary or the objectives.

To view the 'JIRA Blockers' report:

  1. Click the dropdown arrow next to the Reviews tab at the top of the page and select Reports.
  2. Click JIRA Blockers (under the 'Reports' sub-tab).
  3. Enter details for your JIRA server and project, and click Go. 

The 'JIRA Blockers' report displays the following information:

    • A list of JIRA issues for which one or more Crucible reviewers has not completed their review.
    • A list of users who have an incomplete Crucible review that relates to a JIRA issue.
    • A list of open JIRA issues for which a Crucible review is closed, and vice versa.

Screenshot: 'JIRA Blockers' Report

  • No labels

2 Comments

  1. Anonymous

    Why can't we select multiple projects for this report? This breaks the Scrum approach where multiple projects are part of single application.

  2. Ankita Gupta

    Hi,

    I downloaded atrial version of Crucible. I was looking for the review results that this tool will generate on the basis of some criterions(JAVA coding standards) and report them on a dashboard. What I found here is we generate a review and attach some source code, highlight the lines to be reviewed and assign them to the reviewers, which they manually review and post comments based on their findings.

    My query is how this crucible tool is automating the process of code review findings?

    Please revert with the details.

 

 

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