> 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/operations/quality-control/quality-gates.md).

# Quality Gates

A quality gate is a set of conditions on measured values, such as "Critical issues equal to 0". After an assessment, IZ Suite compares the application's measured values with the gate for its technology and records a pass or a failure. Use this tab to see which applications each gate judged, investigate failures and adapt the conditions for each technology.

Open it from **Operations** → **Quality Control** → **Quality gates** in the sidebar.

{% hint style="warning" %}
You need a role that can view quality gates. Creating, editing and assigning gates, and removing conditions, need roles that can create, edit or delete quality gates.
{% endhint %}

<figure><img src="https://1912836914-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F9vAxMuDrkUkB4OXlH9CL%2Fuploads%2F83K6zWwILB4VDdHtVupA%2Fv2-qc-gates.png?alt=media&amp;token=cf883332-9d9f-4ba9-82ce-f03a3d57ed96" alt="Quality gates tab with summary tiles, filters and the gate library"><figcaption></figcaption></figure>

## Summary Tiles

Click a tile to filter the gate library.

| Tile                   | Shows                                                              |
| ---------------------- | ------------------------------------------------------------------ |
| **Available gates**    | All gates that match the current search and technology.            |
| **Supplied standards** | Built-in gates supplied with IZ Suite, one default per technology. |
| **Your standards**     | Custom gates your team maintains.                                  |

## Gate Library

| Filter                   | Description                                                                                 |
| ------------------------ | ------------------------------------------------------------------------------------------- |
| **Status**               | **All gates**, **Custom**, **Supplied** or **Needs definition** (gates without conditions). |
| **Technology**           | The technology the gate measures, for example Apex, Mule or CloudFormation.                 |
| **Search quality gates** | Finds gates by name.                                                                        |

**Saved filters** and **Save filters** keep a combination of filters for later. **Refresh** reloads the list, **Columns** chooses the visible columns and **Export** downloads the list.

| Column                    | Description                                                                                                                                                                          |
| ------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
| **Quality gate**          | The gate name and a **Supplied** or **Custom** tag. Click the name to open the gate's details.                                                                                       |
| **Technology**            | The technology the gate applies to.                                                                                                                                                  |
| **Conditions**            | The number of conditions, or **Needs definition** when there are none.                                                                                                               |
| **Last updated**          | When the gate last changed. The list shows the most recently changed gates first; click **Last updated** or **Quality gate** to sort by it.                                          |
| **Latest assessment use** | How many applications were assessed with the gate in their latest assessment, how many passed and failed, and in how many organizations it is the default. Click it to review usage. |
| **Actions**               | **Edit gate** (**View gate** when you can only view) and **Assign to organizations**.                                                                                                |

{% hint style="info" %}
Pass and fail counts come from each application's latest assessment only. Several gates can serve the same technology; organization defaults and application selections decide which one an assessment uses.
{% endhint %}

## Gate Details

Click a gate's name, condition count or usage to open its details. The drawer shows the technology, whether the gate is supplied or custom, when it was last updated and its conditions. **Application usage & defaults** shows:

* **Applications assessed**, **Passed this gate** and **Failed this gate** for the latest recorded assessments.
* **Applications using this standard**: each application or version whose latest assessment used this gate, filtered by **All**, **Passed**, **Failed** or **Not evaluated**.
* **Organization defaults**: the organizations that use this gate by default.

**Edit / inspect definition** opens the gate editor. **Assign to organizations** opens the assignment described below.

## Create a Quality Gate

1. Click **Create quality gate**.
2. Enter the **Gate name**. Required.
3. Choose the **Technology**. Required. Conditions measure this technology's metrics, so choose it first.
4. Under **Overall code**, click **Add condition** and fill in the condition (see **Condition Fields** below). Repeat for each condition.
5. Optionally, under **New code**, add the conditions that judge pull requests.
6. Click **Create quality gate**. The gate and its conditions are saved together and the gate opens in the editor.

<figure><img src="https://1912836914-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F9vAxMuDrkUkB4OXlH9CL%2Fuploads%2FIppgIkqmHeUGjbBNf6io%2Fv2-qc-gate-editor.png?alt=media&amp;token=cb13d996-0cea-45dc-b936-994dab8751ee" alt="Quality gate editor with gate identity and overall code conditions"><figcaption></figcaption></figure>

### Condition Scopes

| Scope            | How it is used                                                                                                                                                                                                                                                                                                                                                              |
| ---------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Overall code** | Branches and versions are judged on these conditions: every measured value must satisfy its condition. Findings under an approved, unexpired exception do not count.                                                                                                                                                                                                        |
| **New code**     | Pull requests are judged on these conditions alone: issue counts for the findings that are not open on the target branch, and the vulnerable dependencies or deprecated assets the target branch does not have. Without new-code conditions, or when the target branch has not been scanned, a pull request is judged on the overall conditions, using all of its findings. |

### Condition Fields

| Field                   | Description                                                                                                                                                                                           |
| ----------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Measured value**      | The metric to check, shown with its output type. Required. Boolean metrics cannot be chosen. New-code conditions use issue counts per severity, **Vulnerable Dependencies** or **Deprecated Assets**. |
| **Required comparison** | **Is Greater Than**, **Is Greater Than Equal To**, **Is Less Than**, **Is Less Than Equal To** or **Is Equal To**. Required. Text metrics allow **Is Equal To** only.                                 |
| **Required value**      | The value to compare with. Required. A numeric metric needs a valid number.                                                                                                                           |

The dialog shows the resulting requirement in words, for example "Require Critical Issues to be equal to 0".

### Vulnerable Dependencies and Deprecated Assets

Two measured values let a gate fail on the risks shown on an application's **Risk & lifecycle** panel:

| Measured value              | What it counts                                                                                                                                          |
| --------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Vulnerable Dependencies** | The application's own components that match a vulnerability advisory.                                                                                   |
| **Deprecated Assets**       | The deprecation and lifecycle rules that apply to the application: deprecated components it uses, and the application itself when a rule deprecates it. |

* They are counted only for a technology whose gate has one of these conditions; other gates are not affected.
* IZ Suite counts them when it judges the gate, from the components the assessment collected, and records the counts with the assessment. A later advisory or rule changes the next assessment, not a recorded result.
* Only the application's own risk counts, not the risk of the applications it connects to. Matches reviewed as **Fixed**, **Won't fix** or **Exception**, and rules not yet in effect, do not count.
* As **New code** conditions, they count only what a pull request adds: the vulnerable dependencies and deprecated assets its target branch does not have.

A failed condition names what was found, for example "1 - Vulnerable Dependencies (log4j-core 2.14.1: CVE-2021-44228), which is greater than configured value of 0". See [Risk & Lifecycle](https://knowledgebase.autorabit.com/product-guides/integral-zone/iz-suite/workspaces/dependency-insights/risk-and-lifecycle.md) for the advisories and rules behind them.

{% hint style="info" %}
For example, allow existing debt on the branch with the overall condition **Deprecated Assets** is at most 5, and stop pull requests from adding risk with the new-code condition **Vulnerable Dependencies** is at most 0.
{% endhint %}

## Edit a Quality Gate

1. Click **Edit gate** on the gate's row.
2. Change the **Gate name** and click **Save gate details**.
3. On **Required conditions**, use **Add condition**, **Edit condition** or **Remove condition** in each scope. Each change is saved when you confirm it.

The **Technology** cannot be changed while the gate has conditions; remove them first. The **Application usage & defaults** tab shows the same usage as the details drawer and **Assign organization defaults**.

{% hint style="warning" %}
The evaluator skips missing measurements and Boolean conditions. A recorded pass alone does not prove that every condition was evaluated, so check that the profile for the technology measures each metric your gate uses.
{% endhint %}

## Assign a Gate to Organizations

1. Click **Assign to organizations** on the gate's row. The **Activate Profile In Org** dialog lists the organizations that already use the gate under **Profile active in Organizations**.
2. Choose one or more organizations in the **Add organization to profile** field.
3. Click **Add Organizations**.

Assignment controls which organizations use the gate for future assessments. It does not change past assessment results.

## Next Steps

* [Metric Profiles](https://knowledgebase.autorabit.com/product-guides/integral-zone/iz-suite/operations/quality-control/metric-profiles.md): make sure the metrics your conditions use are measured.
* [Metric Rules](https://knowledgebase.autorabit.com/product-guides/integral-zone/iz-suite/operations/quality-control/metric-rules.md): review what each measured value means.
* [Quality Profiles](https://knowledgebase.autorabit.com/product-guides/integral-zone/iz-suite/operations/quality-control/quality-profiles.md): choose which rules raise the findings that gates count.
* [Quality Control](https://knowledgebase.autorabit.com/product-guides/integral-zone/iz-suite/operations/quality-control.md): return to the Quality Control overview.


---

# 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/operations/quality-control/quality-gates.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.
