> 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/integral-zone/iz-suite/workspaces/code-analysis/findings.md).

# Findings

The **Findings** tab of Code Analysis lists the open findings in the latest assessment of each branch you can see, grouped by rule or file. It also estimates the effort to fix them and keeps the register of exceptions.

Open it from **Workspaces** → **Code Analysis** → **Findings** in the sidebar.

{% hint style="info" %}
Requires the **Code Analysis** licence.
{% endhint %}

<figure><img src="https://1912836914-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F9vAxMuDrkUkB4OXlH9CL%2Fuploads%2FjoIexFVeEszq6H6h0TzH%2Fv2-code-findings-open.png?alt=media&amp;token=ec689886-0533-4074-8589-a3abac8a54db" alt="Open findings grouped by rule with the New code only switch and table tools"><figcaption><p>Open findings</p></figcaption></figure>

## Filters and tiles

The filter bar has **Organization**, **Source** and **Asset type**; the **Filters** panel adds **Severity**, **Category**, **Rule** and **Security standard**. The metric tiles are the same as on the [Overview](https://knowledgebase.autorabit.com/product-guides/integral-zone/iz-suite/workspaces/code-analysis/overview.md#metric-tiles) tab.

## Open findings

| Control           | Description                                                                                                                                                |
| ----------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Grouping          | **By rule**, **By file** (one row per file, with its severity mix) or **Occurrences** (one row per finding).                                               |
| **New code only** | Only findings the change introduced: for a pull request, findings not open on its target branch; for a branch, findings new since its previous assessment. |

| Column          | Description                                                                                           |
| --------------- | ----------------------------------------------------------------------------------------------------- |
| **Finding**     | Rule name, the number of applications and the asset type; for a single occurrence, the file and line. |
| **Severity**    | Blocker, Critical, Major, Minor or Info. Sortable.                                                    |
| **Category**    | Vulnerabilities, Bugs, Security hotspots or Code smells.                                              |
| **Occurrences** | Open occurrences in the group. Sortable.                                                              |
| **Assessed**    | When the assessment was recorded. Sortable.                                                           |

Click **Inspect occurrences** on a group to list its occurrences (**Location**, **Application**, **Status on branch**, **Assessed**), and **Back to groups** to return. **Status on branch** is **New**, **Reopened**, **Already open**, or shows an exception request. Above the list, Refresh reloads it, Columns chooses the columns shown and Export this page downloads the current page.

## Finding detail

Click **Read finding** to open the detail: severity and category, **What was found** (application, location, change), the affected code when the assessment retained the files, **How to fix**, **About the rule** with **Open this rule in Quality Control**, and **Capture details**. The layout is the same as in Platform Analysis.

### Mark a finding as a false positive or accepted risk

1. In the finding detail, click **Mark as false positive / accept risk**.
2. Choose the **Kind**: **False positive** or **Accepted risk**.
3. Enter the **Reason** (required, at least 10 characters).
4. Set **Expires after (days)**: 90 unless you choose otherwise, at most 365.
5. Click **Request exception**.

Another person with edit access to the application decides the request. An approved exception stops the finding counting towards the quality gate and the open-finding counts on every branch of the application until it expires.

## Time to fix

The **Time to fix** sub-tab estimates the work to fix the open findings: **By severity and category**, **By rule** (with **Per finding** effort and an **Auto-fix** tag) and **By application**. Select a severity in By severity and category to estimate only that severity. Findings under an approved exception are left out, and a day is 8 working hours. See [Platform Analysis Findings](https://knowledgebase.autorabit.com/product-guides/integral-zone/iz-suite/workspaces/platform-analysis/findings.md) for the columns.

## Exceptions

The **Exceptions** sub-tab shows the **In force**, **Expire in 30 days**, **Lapsed**, **Awaiting a decision** and **Revoked** tiles and the **Exception register** (**Application**, **Finding**, **Kind**, **Requested by**, **Decided by**, **Status**, **Expires**). Use **Approve exception**, **Reject exception** or **Revoke exception** on a row.

{% hint style="warning" %}
Deciding or revoking an exception needs edit access to the application. The person who requested an exception cannot decide it.
{% endhint %}

## Next Steps

* [Branches & Baselines](https://knowledgebase.autorabit.com/product-guides/integral-zone/iz-suite/workspaces/code-analysis/branches-and-baselines.md): open the dossier of an affected branch.
* [Pull Requests](https://knowledgebase.autorabit.com/product-guides/integral-zone/iz-suite/workspaces/code-analysis/pull-requests.md): see the findings each pull request introduced.
* [Quality Rules](https://knowledgebase.autorabit.com/product-guides/integral-zone/iz-suite/operations/quality-control/quality-rules.md): review the rules behind the findings.
* [Code Analysis](https://knowledgebase.autorabit.com/product-guides/integral-zone/iz-suite/workspaces/code-analysis.md): back to the workspace.


---

# 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/integral-zone/iz-suite/workspaces/code-analysis/findings.md?ask=<question>&goal=<user_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.
