> For the complete documentation index, see [llms.txt](https://docs.sealights.io/knowledgebase/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.sealights.io/knowledgebase/coverage-and-quality-insights/user-story-coverage/coverage-analysis-for-azure-devops-ado/project-settings.md).

# Project settings

{% hint style="info" icon="user" %}
Audience: ADO **project administrators**.
{% endhint %}

### About project settings

#### What it provides

A place for each project to decide **how coverage is measured** and **what "good" looks like** for that team. You choose which test stages make up the main coverage result, define additional views of coverage for your team, and set the thresholds that turn percentages into healthy, warning, or critical signals.

#### Why it matters

Teams don't all test the same way. Settings per project let each team see coverage the way it works: a team that relies on unit and component tests can measure exactly those, and a team with strict release criteria can set a higher bar than a team still building up its tests.

#### When to use it

* When you set up a project for the first time.
* When your team starts reporting a new test stage, or changes which stages count.
* When you want an extra view of coverage, such as unit tests only, or everything except unit tests.
* When your quality bar changes.

#### Decide before you start

* Which test stages should count toward the main coverage result (the headline number)?
* Which additional views does your team want to see next to it?
* What coverage level is healthy for your team, and at what level should it be flagged as a risk?

> Organization settings must be done first. See [Organization settings](https://docs.sealights.io/knowledgebase/coverage-and-quality-insights/user-story-coverage/coverage-analysis-for-azure-devops-ado/organization-settings.md).

***

### Understanding the settings

#### Open the page

In ADO, open **Project settings** (bottom-left of the project). Select **Coverage Analysis**.

The page has two cards, **Metrics Definition** and **Coverage Thresholds**. Each card has its own **Save** button, so you can configure and save them independently.

#### Metrics Definition

This card shows **Defined** once a main metric has been saved. Select the card to expand it.

<div align="left"><figure><img src="https://1255034336-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FxSagdStwf6CJ9cI6lA68%2Fuploads%2FqnXfXegYzqVRy24ulHeU%2FScreenshot%202026-10-31%20at%2007.42.40.png?alt=media&amp;token=b0a33294-4c64-4a46-815c-44a3c8c63806" alt="" width="563"><figcaption></figcaption></figure></div>

**Main metric.** The main metric is the headline coverage result: the big percentage shown on work items and in the cross-project view. Use the **Change Coverage** field to choose which test stages it includes. You can pick one stage or several; the result then reflects the code covered by any of the selected stages.

**Secondary metrics.** Secondary metrics are optional extra views of coverage that appear as tags next to the main result. Each one is a name plus one or more test stages, so it can be a single stage (for example, *Unit Tests*) or a custom combination of stages (for example, *Non-Unit Tests*, covering everything except unit tests).

* Your existing secondary metrics appear as tags at the top of the section. If none exist yet, you'll see a note saying so.
* To add one, select **+ Add Metric**, enter a name, choose its test stages, and select **Add**. Add stays unavailable until both a name and at least one stage are chosen.
* To edit one, change its name or stages in its row and select **Change**.
* To remove one, select the trash icon. It disappears from the tags right away.
* Select **Save** to apply your changes.

#### Coverage Thresholds

Thresholds add a quality signal to coverage. Use the switch on the card to turn them on or off.

<div align="left"><figure><img src="https://1255034336-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FxSagdStwf6CJ9cI6lA68%2Fuploads%2F8rbgKuMF1piYUMYZ4clp%2FScreenshot%202026-10-31%20at%2007.42.25.png?alt=media&amp;token=143acb5c-49f0-4a91-9289-71c82cc595e7" alt="" width="563"><figcaption></figcaption></figure></div>

* **Off:** work items show coverage without a quality status, and all results appear in neutral blue.
* **On:** the card expands and you set two values:
  * **Target Coverage:** at or above this value, coverage is **Healthy** (green).
  * **At-Risk Threshold:** below this value, coverage is **Critical** (red).
  * Anything in between is a **Warning** (orange).

Both values are whole numbers from 0 to 100. The target must be higher than the at-risk value.&#x20;

Select **Save** to apply. The new colors then appear on work items and in the cross-project view.

### What's next

See your coverage: [Coverage on a work item](https://docs.sealights.io/knowledgebase/coverage-and-quality-insights/user-story-coverage/coverage-analysis-for-azure-devops-ado/work-item-coverage-insights.md) and [Cross-project coverage view](https://docs.sealights.io/knowledgebase/coverage-and-quality-insights/user-story-coverage/coverage-analysis-for-azure-devops-ado/cross-project-coverage-view.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.sealights.io/knowledgebase/coverage-and-quality-insights/user-story-coverage/coverage-analysis-for-azure-devops-ado/project-settings.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.
