iCR for Python User Guides
iCR for Python 3.0
iCR for Python 3.0
  • Table of contents
    • Introduction
    • Overview
    • Getting Started
      • Installing iCR for Python
      • Managing your service
        • Opening Ports
      • Authorizing Access to Your Source Code
        • Authenticating GitHub Access with a Cloud-Based VCS Repository Service
          • Authenticating GitHub Access with a Private VCS Repository
        • Authenticating GitLab Access with a Cloud-Based VCS Repository
          • Authenticating GitLab Access with a Private VCS Repository
        • Authenticating Bitbucket Access with a Cloud-Based VCS Repository
          • Authenticating Bitbucket Access with a Private VCS Repository
          • Setting Bitbucket Server Credentials in the Navigator
    • Using the Navigator
      • Connecting to the Navigator
      • Setting your private passphrase
      • The Navigator top banner
      • The Analysis Engine status
      • Selecting Your Source Code
        • Using a cloud-based VCS
        • Selecting your branch
        • Using a private VCS
        • Using a local project
        • Setting the scope of your analysis
      • Integrating with your bug tracking system
        • Integrating with Jira - Define Your Project
        • Integrating with Jira - Authorizing Access for iCR
        • Integrating with Jira - Connecting with iCR
    • Using the Analysis Engine
      • Initiating an analysis
      • Monitoring the analysis
      • Interrupting the analysis
    • Reviewing your results
      • Reviewer summary and filters
      • Filter by Directory pane
      • Filter by Category pane
      • Reviewing a fix
      • Accepting a fix
        • Accepting a fix when integrated with your bug system
      • Rejecting a fix
        • Rejecting a fix when integrated with your bug system
      • Undoing a fix
        • Undoing a fix when integrated with your bug system
      • Rejected fix history
      • Providing feedback
      • Applying the fixes
      • Cases needing manual attention
      • Capturing results for printing or sharing
      • Ending a reviewer session
    • When you are complete
    • Appendix – List of supported fixers
    • Appendix – Example Summary Report
    • Appendix - Sample Bug Listing
Powered by GitBook
On this page
  1. Table of contents
  2. Reviewing your results

Filter by Category pane

PreviousFilter by Directory paneNextReviewing a fix

Last updated 1 year ago

Another way to filter the set of reviewable fixes is by constraining the various classes of fixers that are to be reviewed using Filter by Category. When the Reviewer is first launched, all of the categories are selected by default. This is indicated by showing that the Select All box is checked, and each individual category box is checked.

When all categories are selected and the entire project directory is selected, the summary will show all fixes that are available for review. In this example, that is 92.

Category filters are combined with the directory filter to limit the fixes summaries to only those fixes within that directory subtree AND the selected categories.

You may want to ONLY review fixes in a single category. In this case, you may click on the Select All option. Doing that deselects all of the categories. Then, you can click on only the one (or multiple) categories of particular interest. Clicking Select All will reset the category filters and all fixes will be displayed again.

If there is a directory subtree selected, only fixes in that category within the selected subdirectory or file will be shown.

In the example provided here, we have selected only those fixes in the Sensitive Data Exposure category. Because of that, the summary at the top of the Fixes pane is updated to reflect that now, only 7 fixes are Selected for review. Note that the Unresolved tab also reflects this.