Use the Test Folder Traceability Summary gadget to review testing for selected repository folders. It shows coverage, outcomes, untested work, and Jira work items linked to the relevant Test Runs.
Add and configure the gadget
Open a Jira dashboard you can edit and use Add gadget.
Find Vansah - Test Folder Traceability Summary and add it.
Open the gadget’s configuration.
Choose the Jira space or spaces, then select the Test Folders you want to report on.
Review the selected folders, including any subfolders selected by the picker.
Set any needed filters, then select Save.
The screenshots show an older layout. You need access to the selected Jira spaces and reporting data.
Read the report
Metric | Meaning |
Total Linked Cases | Cases linked in the selected folder context and matching the filters. |
Coverage | Completed testing as a percentage of the included cases. It is not source-code coverage. |
Passed / Failed | Completed outcomes. Pass and fail rates exclude completed N/A outcomes. |
Untested | Cases without a completed, in-progress, or blocked outcome in the report’s applicable execution scope. |
Blocked | Cases or executions currently blocked in that context. |
Test Run Issue | Jira work items linked to the relevant runs. These are not necessarily confirmed defects. |
The report uses the latest applicable run for each case version and folder under its filters. It is not a count of every historical run.
Investigate a count
Select a linked count in the summary or a folder row.
Review the detail list’s title and folder context.
Open a case or run to inspect its result and evidence.
Refresh the report after changing testing records.
See Open Test Cases from a Vansah Gadget for detail-list behavior. Execution and edit actions still require their corresponding permissions.
Compare totals correctly
A Test Case can be reused in several folders. Summary totals add folder contributions; they are not necessarily a unique count across the Jira space.
Check selected folders and case versions when comparing with the repository tree.
Date, environment, release, sprint, and case-property filters can change the included data.
Review N/A, blocked, in-progress, and untested counts alongside pass rate. A high pass rate alone does not show that testing is complete.
For a broader execution overview, see the Test Summary Report gadget.