---
## Quality Gates
**Quality Gate Status** (`alert_status`)
-State of the Quality Gate associated to your Project. Possible values are : `ERROR`, `WARN`, `OK`
+State of the Quality Gate associated to your Project. Possible values are : `ERROR`, `OK`
+WARN value has been removed since 7.6.
**Quality Gate Details** (`quality_gate_details`)
For all the conditions of your Quality Gate, you know which condition is failing and which is not.
### Portfolios Home Page
-The Portfolio Home Page is the central place for managers and tech leads to keep an eye on the Releasability of the projects under their supervision. Releasability is based on the project's quality gate: green or orange (pass or warning) is releasable. Red (error) is not. Each Portfolio home page offers an aggregate view of the releasability of all the projects in the Portfolio.
+The Portfolio Home Page is the central place for managers and tech leads to keep an eye on the Releasability of the projects under their supervision. Releasability is based on the project's quality gate: green (pass) is releasable. Red (error) is not. Each Portfolio home page offers an aggregate view of the releasability of all the projects in the Portfolio.
At the top of the page, you can easily see whether overall Portfolio is currently rated as releasable and if any projects in the Portfolio have failed their Quality Gate. And the Reliability, Security, and Maintainability ratings show the overall health of the Portfolio in these three domains, along with an indicator of the worst-performing project(s) in each domain.
### Releasability Rating
-The Releasability Rating tells you the ratio of projects in the Portfolio that do NOT have a **FAILED** Quality Gate (ie QG being **PASSED** or **WARNING**) :
+The Releasability Rating tells you the ratio of projects in the Portfolio that do NOT have a **FAILED** Quality Gate (ie QG being **PASSED**) :
**A**: > 80%
**B**: > 60%
Since the [Quality Gate](/user-guide/quality-gates/) is your most powerful tool to enforce your quality policy, the page starts with the project's current Quality Gate status. If the project passes, a simple, green all-clear is shown.
-If not, details and drill-downs are immediately available to quickly identify what went wrong, with a section for each error or warning condition showing what the current project value is and what it should be. As usual, you'll be able to click through on current values to get to drilldowns.
+If not, details and drill-downs are immediately available to quickly identify what went wrong, with a section for each error condition showing what the current project value is and what it should be. As usual, you'll be able to click through on current values to get to drilldowns.
## What should I fix first?
Because the best way to improve a project's quality is to catch and fix new problems before they become entrenched, the first view of a project is centered around the New Code Period, which is highlighted in yellow on the right of the project homepage. The project space page shows a high-level summary of critical metrics, both current values and their New Code Period values.
Each Quality Gate condition is a combination of:
* measure
-* period: **Value** (to date) or **New Code** (differential value over the New Code period)
* comparison operator
-* warning value (optional)
-* error value (optional)
+* error value
For instance, a condition might be:
* measure: Blocker issue
-* period: Value
* comparison operator: >
* error value: 0
Smart notifications allow developers using Connected Mode in SonarLint to receive in-IDE notifications from {instance} when:
-* the Quality Gate status (failed / success / warning) of a project /solution _open in the IDE_ changes
+* the Quality Gate status (failed / success) of a project /solution _open in the IDE_ changes
* a {instance} analysis raises new issues _introduced by this developer in a project /solution open in the IDE_
## Activate/deactivate Notifications
-For each Quality Gate condition you must choose the metric to be tested, the threshold at which to raise a warning or error, and whether or not to apply the condition to all code or only to New Code period (irrelevant for conditions "on New Code").
+For each Quality Gate condition you must choose the metric to be tested, the threshold at which to raise an error, and whether or not to apply the condition to all code or only to New Code period (irrelevant for conditions "on New Code").
---