> For the complete documentation index, see [llms.txt](https://docs.sonarsource.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.sonarsource.com/sonarqube-server/quality-standards-administration/managing-quality-gates/quality-gate-history.md).

# Quality gate history

In SonarQube Server 2026.5, quality gate history helps you monitor guardrails adherence and understand whether your project is actually following its configured quality gate over time.

A quality gate only protects your codebase when teams respect it during development and release workflows. This feature adds visibility into releases that happened while the quality gate was failing, so you can spot risky practices and improve your delivery process.

This feature is available only for projects that use the [Quality standards and new code](/sonarqube-server/user-guide/about-new-code.md#previous-version) new code definition.

## Viewing the quality gate history <a href="#viewing-the-quality-gate-history" id="viewing-the-quality-gate-history"></a>

To open the quality gate history of a project, do one of the following:

* Go to *Your project* > **Reporting** > **Quality gate history**.
* On the project's **Summary** page, click the quality gate history icon next to the quality gate status. To open the **Summary** page, go to *Your project* > **Analysis** > **Summary**.

## What this feature shows <a href="#what-this-feature-shows" id="what-this-feature-shows"></a>

The feature focuses on the main branch only. It provides a project-level view of quality gate history across released versions, including:

1. Period filters for **30 days**, **6 months**, **1 year**, and **All time**.
2. A summary of safe versus risky releases.
3. Whether each release was safe or risky at release time.
4. A timeline of released versions.

A release is considered risky when the quality gate was failing at the time the version was released.

## How the quality gate history works <a href="#how-the-quality-gate-history-works" id="how-the-quality-gate-history-works"></a>

This view helps engineering managers and DevOps leads identify when code is being promoted despite failing the quality gate. Repeated risky releases can indicate that guardrails are configured but not enforced in practice.

If you see risky releases, review your delivery workflow and CI configuration. You can configure your CI tool to [Not integrated CI tools](/sonarqube-server/analyzing-source-code/ci-integration/not-integrated-tools.md#quality-gate-fails), which helps prevent risky releases from being promoted.

## Related pages <a href="#related-pages" id="related-pages"></a>

* [Quality standards and new code](/sonarqube-server/user-guide/about-new-code.md)
* [Not integrated CI tools](/sonarqube-server/analyzing-source-code/ci-integration/not-integrated-tools.md#quality-gate-fails)
* [Understanding quality gates](/sonarqube-server/quality-standards-administration/managing-quality-gates/introduction-to-quality-gates.md)
* [Managing quality gates](/sonarqube-server/quality-standards-administration/managing-quality-gates.md)


---

# 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://docs.sonarsource.com/sonarqube-server/quality-standards-administration/managing-quality-gates/quality-gate-history.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.