Page History
...
- 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 resoluton
- Include Previous Versions: take into account previous versions when searching for a requirement
It's also possible to configure the report with additional parameters:
- Hide Test Runs: hides the Test Runs column; this is quite useful when you are using Continuous Integration and you have multiple runs
...
Analysis
On the left side, 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.
...
The report not only shows the traceability between entities, but it also presents some calculated values for the selected options. For example, the requirement status and the Test status that are shown in the Requirements and Tests columns, respectively.
| Column | Notes |
|---|---|
Requirements | "requirements" and the calculated requirement status, taking into account the options selected for analysis |
| Tests | Tests and the calculated status, taking into account the options selected for analysis |
Test Runs | Test Runs and their status from all related Test Executions |
| Defects | defects directly associated with the Test Runs as well as those directly linked to the Tests (via a "created" issue link) for the given version (through the AffectsVersion). |
...
| Info | ||
|---|---|---|
| ||
The defects that appear on a separate row (i.e., that are not related with a specific Test Run) contain all defects associated with the Test. In other words, it contains all defects linked to the Test, including the ones reported for Test Runs done on a different environment. This allows you to see all "related defects" which may or not impact your version.
|
Example
...
Note: Requirements with Labels or Statuses configured to be ignored in the Requirements Coverage settings will not appear on this report.