A traceability report version built from Jira: each story with its linked cases and defects.

A requirements traceability matrix that builds itself from Jira and GitHub

Link each test case to the stories and issues it verifies. Probara turns those links into a report of every requirement, its test cases, their latest results and the requirements nothing tests yet.

Start freeSee documentation

Traceability reports and the Jira and GitHub integrations they read are part of Pro, and of the 14-day Pro trial every new organization starts on. Compare plans

Link test cases to the requirements they verify

Link a test case to the Jira stories and epics it verifies, or select many cases in the repository and link them to one issue at once. GitHub issues link to a case as a requirement the same way.

Each Jira issue gets a link back to its case. Unlinking only removes the link: the issue stays where it is.

Requirement links
Jira
Stories, epics and other issues, by search or key
GitHub
Issues linked as Requirement
Many at once
A whole repository selection to one issue
Unlink
The issue stays in its tracker

One report for the requirements you choose

Build a report from the Jira projects and issue types you choose, or from up to 20 GitHub repositories narrowed by labels, milestone and issue state.

A report covers only what you chose, so a release, a team or a component can each have a report of its own.

Report sources
TrackerWhat a report reads
Jira CloudUp to 20 projects, optionally narrowed to issue types
GitHubIssues of up to 20 repositories
GitHub labelsIssues that carry every selected label
GitHub milestoneIssues in that milestone
GitHub issue stateOpen, closed, or both

Versions that keep the coverage you shipped with

Each version of a report is a snapshot of its requirements at the moment it was generated, with their linked test cases, latest results and defects. Once ready, a version never changes.

Generate a new version before each release and keep the earlier ones to compare. Versions are numbered, can be renamed, and generate in the background while you keep working.

A version
Snapshot
Requirements, cases, results and defects
Frozen
Later edits in Jira or Probara do not change it
Numbered
Version 1, 2, 3, with a name of your own
Size
Up to 5,000 requirements

Every requirement with its tests, results and defects

Requirements that a test case covers sit in Linked; the ones nothing covers sit in Unlinked, so testing gaps show up before a release does.

Unfold a requirement to see each linked case with its latest result and the defects linked to it. A case is marked when its requirement changed after the case was last edited.

A traceability report version built from the acme-dev/web GitHub repository: 9 GitHub issues, 78% with linked cases, with one issue unfolded to its test cases and their latest results.

Find the gaps, then export them

Search requirements by key or title and combine filters to find what matters before a release: requirements still in progress, cases that last failed, open defects.

Export the current tab, search and filters as CSV, one row per requirement with its linked cases and defects. It works the same for Jira and GitHub reports.

Filters
Requirement status
To do, In progress or Done
External project
The Jira project a requirement belongs to
Latest run result
Passed, Failed, Blocked, Skipped or Not run
Defect status
Open, In progress, Resolved or Closed

Build reports from a script or an AI assistant

Scripts and CI jobs create reports, generate versions and read their requirements over the traceability reports API, with an API token.

AI assistants your team already uses do the same through the traceability tools of the Probara MCP server.

A GitHub report
POST /api/v1/projects/WEB/traceability/reports
{
  "name": "Checkout requirements",
  "filters": {
    "provider": "github",
    "repositories": [{ "connectionUlid": "01J9Z3K4M5N6P7Q8R9S0T1V2W3", "fullName": "acme/shop" }],
    "labels": ["requirement"],
    "milestone": "v2.0",
    "state": "all"
  }
}

More of Probara

See which requirements your tests cover

Create your organization, connect Jira Cloud or GitHub and build your first traceability report. Every new organization starts on a 14-day Pro trial, with no credit card.

Start freeSee documentation