As a user, I can use the Traceability Report

Users must be able to analyse the traceability and coverage using the Traceability Report.

The report must follow the same configure layout as the overall test coverage.

Analysis and Scope

Users can choose the analysis scope for:

• Latest
• Version
• Test Plan

They can still define:

• Final/non-final Test Statuses
• Test Environment

View

• Hierarchical
• Flat

Filters

The filters provided are:

• Project
• Fix Version
• Include previous versions
• Assignee
• Component
• Status
• Resolution
• Contains

Users can also choose a saved filter that can include multiple projects.

Quick Filters

The report must provide a quick filters section to filter requirements by test status.

Content

The report will be a list of the filtered Covered issues in Jira, where each entry will contain:

Requirement Column

Should display the issue key, workflow status and summary. Users can view the status of the requirement.

Tests Column

Should display the issue key, workflow status and summary. Users can view the status of the test.

Test Runs

Should display the issue key, workflow status, summary, Fix Version, Finished on, executed by and Test Environments. Users can view the status of the test run and navigate to the execution screen.

Defects

Should display the issue key, workflow status and summary.

Additional Settings

Users can still be able to:

• Show/hide Test Runs column
• Configure additional columns on requirement issues
• Configure additional columns on test issues

The report is limited to 1000 issues. If the filters show more than 1000 issues, the report must display a warning message.

Also, this report must display only 20 issues each time. The user can load the remaining issues 20 by 20 in the end of the page.

Test runs must also be limited to 5 in each Test. Users are able to "load more" (another 5) in this view.