> For the complete documentation index, see [llms.txt](https://knowledgebase.autorabit.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://knowledgebase.autorabit.com/product-guides/codescan/issues/about-issue-status.md). # About Issue Status ## **Issue Status** An issue can have the following statuses: * **Open**: This is the initial status assigned by CodeScan when a new issue is detected during an analysis. (**Reopened:** A user can reopen a False positive, Accept Issues. If a fixed issue still exists after the next analysis, CodeScan automatically reopens it, indicating that the fix was unsuccessful.) * **Accept (Won’t Fix)**: Select if the user decides not to fix the issue and thinks the rule is irrelevant in this context. * **False Positive (Analysis is mistaken):** Set by an authorized user if the analysis is mistaken. (This issue can be suppressed if it was not raised accurately.). CodeScan ignores false-positive issues in the quality reports and code ratings. * **Confirmed (deprecated)**: An issue is moved to Confirmed when a user manually validates it as a valid issue that needs to be addressed. Note: CodeScan ignores confirmed issues in the code ratings but displays the number of confirmed issues in various analysis snapshots in the UI. * **Fixed (deprecated)**: Set by an authorized user if the confirmed issue has been resolved in the code (i.e., it is no longer detected) and is waiting for the subsequent analysis to close it, or reopen it if it was not actually fixed.

If users mark many issues as False Positives, it means that some coding rules are inappropriate for the project. In that case, rules can be deactivated in the quality profile, or the project's analysis scope can be adjusted to exclude files. The following diagram shows the Issue life cycle:

### **Tracking Issue History** 1. Under the **Issues** tab, select the violation for which you want to check the history of changes. 2. You should be able to see when the Issue was introduced in the upper corner of the issue page.

3. In the Activity tab, you should see the history and every activity on the Issue, such as the creation date, member assignment, severity, comments, etc.

--- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://knowledgebase.autorabit.com/product-guides/codescan/issues/about-issue-status.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.