01
Connect
Publish a run with Jira, branch, commit, and project context.
Evidence feature
Give every Jira issue a live automated test signal
Let product, QA, and engineering see whether related tests passed, failed, or changed without leaving the work item.
Last updated July 10, 2026
Direct answer
What is Jira run summaries in Testream?
Testream run summaries bring the automated evidence related to a Jira issue into the issue view, including run status, source context, relevant failures, and suite changes.
The problem
A Jira issue cannot tell the delivery story if the test evidence stays in CI
Issue-level summaries make evidence visible to the people discussing scope, risk, and readiness.
What teams gain
- See related run status inside Jira
- Understand branch and commit provenance
- Review how the connected suite changed over time
How it works
A clear path from setup to useful evidence.
02
Surface
Testream shows relevant evidence on the Jira issue.
03
Follow
Use the summary to open the full run, failure, or history when needed.
Product proof
Readable evidence where delivery work is discussed
Issue-linked run status
Branch and commit context
Failure and artifact drill-down
Suite-change visibility
Continue exploring
Related Testream features
Evidence
Automated reporting
Publish automated test results from CI/CD into Jira with run history, failure evidence, artifacts, and release context.
Evidence
Suite changes
See which automated tests were added, removed, or changed between runs and connect suite movement to Jira work.
Delivery
Issue creation
Create actionable Jira issues from failed tests with error output, run metadata, and evidence already attached.