---
title: "Overall Requirement Coverage Report"
canonical: "https://docs.getxray.app/space/XRAY/301699454/Overall%20Requirement%20Coverage%20Report"
format: markdown
---
> Macro (rw-ui-expands-macro)
>
> > Macro (rw-expand)
>
> > Macro (toc)
# Introduction
The Overall Requirement Report (Figure 1) shows a normalized horizontal stacked bar chart with the current [Requirements](https://getxraydocs.atlassian.net/wiki/spaces/XRAY/pages/301469601) coverage for the selected **Analysis Version **(or** Test Plan**)**, Test Environment, **and **Grouping** field.
The report provides the means to analyze your Requirements statuses in real-time.
> ⚠️ To use this report, your project must have **Requirements Coverage** enabled: check out [Configure Jira project to be used as Requirements project](https://getxraydocs.atlassian.net/wiki/spaces/XRAY/pages/301406021).
To analyze the current status of your release, or even other releases from the past, you need to evaluate the status of Requirements, taking into account the respective results.
You might want to analyze just the Requirements implemented in a given version, or you may want to analyze requirements from earlier versions based on your regression Testing.
# Operations
## Report Access
> Macro (rw-ui-steps-macro)
>
> > Macro (rw-step)
>
> On the top menu of your Jira Data Center instance, click *Projects* (Figure 2 - 1) and select a project (Figure 2 - 2).
>
> 
>
> > Macro (rw-step)
>
> A menu will open on the left side of the screen. There, click *Xray* *Reports* (Figure 2 - 3).
>
> > Macro (rw-step)
>
> Use the dropdown menu at the top of the screen (Figure 3 - 1) and click the *Overall Requirement Coverage Report* (Figure 3 - 2).
>
> 
## Configuring and Using the Report
When the Overall Requirement Coverage report is opened, an empty state will be displayed, and you'll have to explicitly generate the report after selecting the initial filters (Figure 3).
At the top of the report, you have some options that need to be configured:
- **A**: Analysis & Scope, for choosing how to analyze the entities
- **B:** Group by, for defining how to visually group/aggregate items
- **C**: Filter, for selecting the source data
- **D**: Visualization information and options
You need to configure the source data (i.e., the requirements) for the chart and how to calculate the requirement status for each one of the requirements.
## Source data
Source "requirement" issues can be directly provided (within section C) using the j fields configured in the *Basic* tab or the JQL written in the *Advanced* tab.
By default, the *Basic* tab provides the following fields:
- **Project**: Select multiple projects to analyze **(Only available in Xray Enterprise)**
- **Fix Version**: Version assigned to requirements
- **Sprint (Only if Jira Software is installed): **Sprint assigned to requirements
- **Component:** Components assigned to requirements
- **Status: **The issue's workflow status
- **Resolution:** The issue's workflow resolution
- **Contains text:** Filter requirements by text
By clicking on *More*, it's possible to manage which fields will be used to filter the requirements:
- Selecting fields will enable to filter further the requirements
- Unselecting fields will remove them from the search criteria
> ℹ️ The default fields cannot be removed from the dialog
Alternatively to the *Basic*, the *Advanced* tab offers the possibility of filtering the requirements via JQL:
If you wish, you can clear the filter in order to see all Requirements once again. You can do this by clicking on the *Clear* button and then press *Apply*.
There is also an options menu (section D) where you can choose the visualization type for the report:
- **hierarchical - **only the parent requirement issues will be presented in the report, if the filter includes them. Sub-requirements can still be visualized in the overall details table.
- **flatten - **the requirement issues will not consider the parent/child relationship. All parent and child requirements will be considered and showed similarly in the report.
## Analysis
On the left side (within section A), you can define the analysis strategy, i.e., the way you want to analyze the selected/filtered requirements. You can choose either to analyze by **Version** or **Test Plan, **and then complement it with a** Test Environment.**
If you choose analysis by **Version**, then the latest results from Test Executions for the specified version are taken into account. If you choose **Test Plan**, only Test Executions (and related results) associated with the given Test Plan are considered during the calculation of the requirement status.
If you specify the Test Environment, then only the executions that ran in the specified environment are considered.
> ℹ️ **Tips**
> ℹ️
> ℹ️ For more information, please see [Coverage Analysis](https://getxraydocs.atlassian.net/wiki/spaces/XRAY/pages/301662486) and [Understanding coverage and the calculation of Test and requirement statuses](https://getxraydocs.atlassian.net/wiki/spaces/XRAY/pages/301669557).
You can visually group the requirements (within section B) by Priority, Component or other fields, so you can analyze requirements from different perspectives.
> Macro (section)
>
> > Macro (legacy-content)
>
> > Macro (legacy-content)
> ℹ️ **Please note**
> ℹ️
> ℹ️ Some Xray global settings may affect the report (e.g.["Requirement Coverage Strategy", "Ignore Requirements with statuses", "Ignore Requirements with labels", "Ignore Tests with status"](https://getxraydocs.atlassian.net/wiki/spaces/XRAY/pages/301504155))
# Example
Each bar on the chart represents a group of Requirements with a different *value *provided by the grouping field. Stacked within each bar are the Requirements grouped by coverage status: **OK**, **NOK**, **NOT RUN**, **UNKNOWN** and **UNCOVERED**.
Because this is a normalized chart, the bars are always 100% wide.
The Overall Coverage requirements chart is interactive. Hovering over each bar shows a small popup with the information on the specific series (Status, Grouping Field and Percentage). You can deactivate a particular series by clicking it in the series legend.
The chart also supports drill-down to 5 levels of requirements. When a section is selected, a table appears below the chart with the Requirement issues:
For each Requirement issue, the table shows the following indicators:
- Total Tests
- Passed
- Failed
- Unknown
It also contains a column with a progress bar that shows the completeness of a Requirement.
Some values may provide a link, so you can be redirected to the respective entities corresponding to the shown number.
# Sharing the Report
The report can be shared by copying and sending the URL located in the browser's address bar.
When opening the report, the Analysis & Scope, Filter, Group by and Requirement Presentation options will be automatically populated with the values provided in the URL.