> 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/2025.3/project-administration/changing-quality-gate-and-fudge-factor.md).

# Changing quality gate

Changing the project's default quality gate in SonarQube Server 2025.3.

The instance’s default quality gate is applied by default to your project. As a project administrator, you can apply other standards to your project. In addition, you can disable the fudge factor used for quality gate computation for your project. See [Understanding the analysis](/sonarqube-server/2025.3/analyzing-source-code/languages/c-family/understanding-the-analysis.md) for more information.

## Changing the quality gate applied to your project <a href="#quality-gate" id="quality-gate"></a>

1. Retrieve your project. See [Retrieving projects](/sonarqube-server/2025.3/user-guide/viewing-projects/retrieving-projects.md) for more details.
2. Select **Project Settings > Quality Gate**.
3. Select **Always use a specific Quality Gate**, and select the quality gate in the list.
4. Select **Save**.

## Configuring the quality gate fudge factor <a href="#configuring-fudge-factor" id="configuring-fudge-factor"></a>

The quality gate fudge factor refers to a mechanism where conditions on duplication and coverage are ignored until the number of new lines is at least 20. This is used to avoid overly strict enforcement when dealing with small changes, as minor issues might disproportionately impact the overall quality gate status.

The fudge factor is enabled by default in your instance. This global setting is applied to all new projects. Project administrators can override it for their project.

You can enable the fudge factor in the UI as explained below, or by setting the `sonar.qualitygate.ignoreSmallChanges` property to `false` or `true` on the CI/CD host, see [Analysis parameters](/sonarqube-server/2025.3/analyzing-source-code/analysis-parameters.md).

To enable or disable the quality gate fudge factor in the UI for your project:

1. Retrieve your project. See [Retrieving projects](/sonarqube-server/2025.3/user-guide/viewing-projects/retrieving-projects.md) for more details.
2. Select **Project Settings > General Settings > General**.
3. In the **Quality gate** section, unselect or select **Ignore duplication and coverage on small changes**.

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

* [Viewing a quality gate](/sonarqube-server/2025.3/quality-standards-administration/managing-quality-gates/viewing-quality-gate.md)
* [Managing custom quality gates](/sonarqube-server/2025.3/quality-standards-administration/managing-quality-gates/managing-custom-quality-gates.md)
* [Changing default quality gate](/sonarqube-server/2025.3/quality-standards-administration/managing-quality-gates/changing-default-quality-gate.md)
* [Associating a quality gate with projects](/sonarqube-server/2025.3/quality-standards-administration/managing-quality-gates/associating-projects-with-quality-gate.md)
* [Subscribing to notifications](/sonarqube-server/2025.3/user-guide/managing-your-account/subscribing-to-notifications.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/2025.3/project-administration/changing-quality-gate-and-fudge-factor.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.