iCR for Python User Guides
iCR for Python 3.0.2
iCR for Python 3.0.2iCR for Python 3.5iCR for Python 3.0
iCR for Python 3.0.2
iCR for Python 3.0.2iCR for Python 3.5iCR 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
  3. Accepting a fix

Accepting a fix when integrated with your bug system

PreviousAccepting a fixNextRejecting a fix

Last updated 1 year ago

If you have , accepting a fix has an additional consequence. By accepting a fix, when you are integrated with a bug tracking system, the fix will be inserted into your bug database.

Let's look at how this works when using Jira Software to manage the bug database.

In , we created a new project to track bugs from iCR. We named it iCR-Bug-Tracking with a project key of IBT.

When a fix is accepted in the Reviewer, it is automatically inserted into the Jira project. Here is what happens:

  • After accepting the fix, go to the iCR-Bug-Tracking project in Jira

  • List all of the current issues in that project. It will display a new bug with the title matching the iCR fix ID

  • The Description field of the new bug will match the description summary from the Reviewer

  • Scrolling down through the content of the bug, you will see the diffs that are needed to effect the fix identified by iCR

Once in your bug tracking database, you may review it further using your normal DevOps processes.

View these steps in the video below:

integrated iCR into your bug tracking system
Integrating with Jira - Define Your Project