iCR for Python User Guides
iCR for Python 3.0.2
iCR for Python 3.0.2
  • 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

Undoing a fix

PreviousRejecting a fix when integrated with your bug systemNextUndoing a fix when integrated with your bug system

Last updated 1 year ago

Using the above example of SDE-PyRRG-1-2, it may be realized that the fix is, indeed, needed, and that you want to change its status.

Clicking on the Show Diff button, as before, will display the original code and the rejected changes. But you will notice that the buttons at the bottom of the window are different from the Unresolved fixes with a new button at the bottom.

A new Undo button is now available. If it is chosen, then the fix moves back to the Unresolved state where it can be left for further review later.

Since this example is one of a rejected fix, then the other option, to accept it instead, is also offered. So, you can click on the Accept button, and the fix will be moved from Rejected to Accepted.

A similar process works for accepted fixes. Should the user decide to reject it instead, the Reject button is available. Also, as in the example above, the Undo button is also there as so the fix may be moved back to the Unresolved state for later review.

A fix can be moved from any one of Accepted, Rejected and Unresolved states by clicking the appropriate button while displaying a diff.