...

At the top of the report you'll find three areas related with the report and with the data shown in the report.

Image RemovedImage Added

• A: Analysis & Scope, for choosing how to analyze the entities
• B: Filter, for selecting the source data
• C: visualization information and options
• D: Visualization information and optionsE: quick filter based on calculated coverage for the defined scope on (A)

...

• Saved filter: a saved filter containing requirement issues
  
  
• Fix Version: version assigned to requirements
• Assignee: the requirement's assignee
• Key or Summary: the requirement's key or summary
• Status: the workflow status
• Resolution: the workflow resolution
• Include Previous Versions: take into account previous versions when searching for a requirement

Additionaly, in (D) it is possible to filter out requirements based on their current coverage status for the scope defined in (A). By default, all possible coverage status are unchecked meaning that all requirements will be shown no matter in which coverage status they are. You can click on one or more statuses and in that case requirements will be filtered out and they'll show if they match one of the selected statuses.

Image Added

Next to each coverage status, you can quickly evaluate the total amount of requirements. This gives you the ability to quickly find and analyze the requirements having problems or the ones that are not yet covered, for example.

There is also an options menu (section DC) where you can choose the visualization type for the report:  

• Requirement Presentation
  • Hierarchical - the parent/child relationship between requirements will be shown
  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
  • up to two levels (e.g. Epic => Story). In this case the filter need only to include the parent requirements (e.g "Epic")
  • Flatten - the requirement issues will not consider the parent/child relationship. All parent and child requirements will be considered and showed
  similarly
  • at the same level in the report
  . 

...

• • , as long as the filter includes them
• Hide Test Runs: hides the Test Runs column; this is quite useful when you are using Continuous Integration and you have multiple runs 

Image Added

Analysis

On the left side (section A), it's possible to define the analysis strategy, i.e., the way you want to analyze the selected/filtered requirements. You can choose to analyze either by Version or Test Plan, and complement it with a Test Environment.

...

Xray will warn you beforehand whenever the total amount of number of Test Runs exceeds a certain threshold.

...

• use carefully the "Load all" option especially if "Hide Test Runs" is unchecked (this option is available at the top-right side of the report page);
• hide Test Runs column in the report, if the number of runs is considerable high (e.g. > 1000);  the amount of information may overload your browser and it will be hard for you to analyze the report with all that information.

Image RemovedImage Added

Examples

In the following example you can see the hierarchical relation between an Epic and some Stories (hierarchical presentation should be enabled in the report settings - section D).  

 NoteNote: Requirements with Labels or Statuses configured to be ignored in the Requirements Coverage settings will not appear on this report.

...