Rejecting a fix when integrated with your bug system

If you have integrated iCR into your bug tracking system, rejecting a fix has an additional consequence. By rejecting a fix, when you are integrated with a bug tracking system, the rejection decision will be reflected into your bug database.

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

In Integrating with Jira - Define Your Project, 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 rejected in the Reviewer, a new bug report is inserted into the Jira project. Here is what happens:

• After rejecting 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

• At the end of the bug report there is a comment which notes that the fix was rejected along with information about who made that decision

Even though the fix was rejected, it is valuable to know that it was found and consciously rejected. Inserting it into the bug database provides the opportunity to have regular DevOps proecesses review the rejection to ensure that that decision was appropriate.

View these steps in the video below: