Uploaded image for project: 'Crucible'
  1. Crucible
  2. CRUC-2839

Review Summary Reports

    XMLWordPrintable

Details

    • Our product teams collect and evaluate feedback from a number of different sources. To learn more about how we use customer feedback in the planning process, check out our new feature policy.

    Description

      I was surprised to find that there is not a standard, easy to get to (read: from the review's front page)
      that can show the traditional code review output:
      1) List all defects w/ type, location (file/line), and description (I imagine being able to filter by defects/all comments/those with JIRA issues) and potentially also listing the users involved in the discussion of each one.
      2) Summarize review by # defects of each type, # each by severity, time spent by reviewer

      It may be a related item rather than part of the report proper, but the moderator should be able to check off each defect from #1 above as verified.

      Essentially, having a big blank box to summarize the review doesn't really capture what normally happens at the end of a review, at least from
      the basic CMM perspective.

      Attachments

        Issue Links

          Activity

            People

              Unassigned Unassigned
              fe4f2d5b927d Brendan Sibre
              Votes:
              7 Vote for this issue
              Watchers:
              7 Start watching this issue

              Dates

                Created:
                Updated: