> 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/cross-project-coverage-view.md).

# Cross-Project Coverage View

<figure><img src="https://1255034336-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FxSagdStwf6CJ9cI6lA68%2Fuploads%2FKYSfAesDMJKT3z2TlUPp%2FScreenshot%202026-10-29%20at%2014.28.31.png?alt=media&amp;token=017797ea-ab51-45c5-a694-6c9790f26019" alt=""><figcaption></figcaption></figure>

#### What it provides

A dedicated page that shows coverage for a **whole set of work items at once**. Choose a saved query and see an overall result, your team's secondary metrics, and the full work item hierarchy with coverage for each item.

#### Why it matters

It gives leads and managers a single view of quality across a release, a team, or an area, with no need to open work items one by one. Because it uses the saved queries your team already maintains, it adapts to however you organize your work.

#### When to use it

* **Release readiness reviews:** is everything planned for this release tested well enough?
* **Sprint and status meetings:** see which Epics or Features need attention.
* **Comparing areas:** spot which part of the hierarchy is weakest.
* **Reporting:** download the data for reviews and stakeholder updates.

#### Example

Before a release review, an engineering manager selects the "Release 5.2" query. The summary bar is orange. She expands the red Epics, finds the stories with the lowest coverage, turns on the Non-Unit Tests column to see which items are weak beyond unit testing, and downloads the CSV for the meeting.

***

### Understanding the data

#### Opening the page

In your ADO project, select **Coverage Analysis** in the left-hand project navigation.&#x20;

#### Choosing a query

Everything on the page is based on the saved query you select at the top. The list contains only the queries you have permission to view, and starts with "All work items in this project". The page remembers your last selection, so the query is already chosen the next time you visit.

You only see work items you have access to in ADO.

#### The overall result

At the top, the summary bar shows the combined coverage for all work items in the report: the percentage, how many modified methods are covered out of the total, and how many are uncovered. It uses the same colors as the work item panel, based on your project's thresholds, and the threshold is shown under the bar.

Below it, metric tags show your team's secondary metrics (for example, Unit Tests or Non-Unit Tests) across the same set of work items.

#### The work item table

The table shows the work items returned by the query as a hierarchy. The highest level found in the results is the top of the tree. For example, if the query returns Epics and User Stories, Epics are at the top and their stories expand beneath them.

The item count appears above the table. For each work item you see its ID and title (linked to the work item), assignee, priority, status, and its coverage as a colored bar and percentage. You can sort by any of these columns.

**N/A** means there's nothing to measure: no code has been reported yet for the item or its children.

A "Data as of" timestamp at the bottom right shows when the data was last updated.

#### Adding columns

Use **Columns** to add a column for any secondary metric defined in the project settings. This lets you compare, for example, overall coverage with unit test coverage across every work item in the hierarchy.

#### Exporting

**Download CSV** exports the table as you see it, including the hierarchy and all visible columns.

#### Full Analysis

Each row has a **Full Analysis** button that opens the detailed analysis for that work item: which child items, test stages, and methods are behind its coverage. See [Work Item Full Coverage Analysis](https://docs.sealights.io/knowledgebase/coverage-and-quality-insights/user-story-coverage/coverage-analysis-for-azure-devops-ado/work-item-coverage-insights/work-item-full-coverage-analysis.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/cross-project-coverage-view.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.
