> 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/filtering-issues-in-codescan.md). # Filtering Issues in CodeScan [CodeScan's](https://www.codescan.io/) filters feature offers a clear view of the code’s specific errors. 1. Navigate to **Organization > Issues**.

2. Click the **Issues** tab to open a new page with different kinds of filters on the left side.

3. As you can see, many filters will help you determine what kind of an error or a warning you want to work on or view depending on **language preferences**, **type of errors**, **severity**, **rules**, etc. 4. You can filter specific errors by selecting the relevant dropdowns.\ Here are a few screenshot examples of how to select filters and work on them. * Here, you can see the options provided, once you click on the specific filter dropdown category and choose the one which is necessary.

**Issues Type and Severity** To know more about different types of issues raised while running a CodeScan analysis, and issues severities, kindly refer [HERE](https://docs.sonarqube.org/latest/user-guide/issues/). 1. To see similar features for other issues, click on the **dropdown** and see the sub categories of issue. 2. The **Rule** filter enables you to view every instance of a specific issue being found in your project.

3. Click on the highlighted **link** to know the definition of the rule. This will show you the rule description as well as examples to help you learn more about the problem.

--- # 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/filtering-issues-in-codescan.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.