diff --git a/README.md b/README.md
index 2f6ebe50..b0fc4bb8 100644
--- a/README.md
+++ b/README.md
@@ -14,6 +14,12 @@ The firewatch project is in its infancy and currently has limited functionality.
   - If multiple issues are created for a run, the issues will all be related to each other to help with issue.
   - The issues created have a "classification" section that is defined by the user in their firewatch config.
     - This can be used as a "best-guess" for what may have gone wrong during the job's run.
+  - Firewatch searches for duplicate issues and makes a comment on the issues rather than filing a second issue.
+    - This is done using the labels on issues created by firewatch. These labels should consist of the failure type, failed step, and the job name.
+    - If the new failures matches the failure type, failed step, and job name; firewatch will make a comment notifying the user that this failure likely happened again.
+  - If no failures are found, firewatch will search for any open issues on the Jira server provided and add a comment to the issue mentioning that the job has passed since that issue was filed.
+    - This functionality also uses the labels on issues created by firewatch.
+    - **Note:** If you get a notification on an issue, but would like to continue working on the issue without getting notifications, add the `ignore-passing-notification` label to the issue.
 
 ## Getting Started
 
diff --git a/docs/cli_usage_guide.md b/docs/cli_usage_guide.md
index fa11c636..1da7aafe 100644
--- a/docs/cli_usage_guide.md
+++ b/docs/cli_usage_guide.md
@@ -89,7 +89,7 @@ $ firewatch report --fail_with_test_failures
 
 **How Are Duplicate Bugs Handled?**
 
-This tool take duplicate bugs into consideration. When a failure is identified, after the failure has been matched with its corresponding rule in the firewatch config, the firewatch tool with search Jira for any bugs that match the following rules to determine if it is a duplicate:
+This tool takes duplicate bugs into consideration. When a failure is identified, after the failure has been matched with its corresponding rule in the firewatch config, the firewatch tool will search Jira for any bugs that match the following rules to determine if it is a duplicate:
 
 - Any OPEN issues that are in the same Jira project defined in the rule's `jira_project` key
 - **AND** issues that have a label matching the step/pod name that failed
@@ -100,18 +100,41 @@ If any issues are found that match all the conditions above, we can be fairly co
 
 > A duplicate failure was identified in a recent run of the {job name} job:
 >
-> Link: {link to prow job run}
+> **Link:** {link to prow job run}
 >
-> Build ID: {failing build ID}
+> **Build ID:** {failing build ID}
 >
-> Classification: {value of the "classification" key of the matching rule}
->
-> Pod Failed: {name of step/pod that failed}
+> **Classification:** {value of the "classification" key of the matching rule}
+> 
+> **Pod Failed:** {name of step/pod that failed}
 >
 > Please see the link provided above to determine if this is the same issue. If it is not, please manually file a new bug for this issue.
 >
 > This comment was created using firewatch in OpenShift CI
 
+**What about stale issues in Jira?**
+
+This tool has functionality to find open Jira issues that were created for the passing job and created by firewatch. When no failures are found for a job, the firewatch tool will search Jira for any Jira issues that match the following rules:
+
+- Any OPEN issues in the provided Jira server that:
+- has a label matching the prow job name that passed
+- **AND** has a label matching "firewatch" (this is to ensure the open issue is created by the firewatch tool)
+- **AND** does NOT have a label matching "ignore-passing-notification" (this is to allow users to stop future notifications if they need to keep the issue open but don't want the notifications in the future)
+
+If Any issues are found that match all the conditions above, we can be fairly confident that a "passing job" notification should be given in the form of a comment on the issue. The comment looks something like this:
+
+>  **JOB RECENTLY PASSED**
+> 
+> This job has been run successfully since this bug was filed. Please verify that this bug is still relevant and close it if needed.
+> 
+> **Passing Run Link:** {link to prow job run}
+> 
+> **Passing Run Build ID:** {passing build ID}
+> 
+> *Please add the "ignore-passing-notification" tag to this bug to avoid future passing job notifications.*
+> 
+> This comment was created using firewatch in OpenShift CI.
+
 ### `jira_config_gen`
 
 The `jira_config_gen` command is used to generate the Jira configuration file used when firewatch interacts with a Jira server.