01
Inspect
Confirm the failure and its available evidence.
Delivery feature
Turn a failed test into a useful Jira issue in one step
Carry the evidence forward automatically so the assignee starts with context instead of asking QA to reconstruct it.
Last updated July 10, 2026
Direct answer
What is Issue creation in Testream?
Testream Issue Creation turns a failed automated test into an actionable Jira issue while preserving the error, run details, and connected artifacts that explain the failure.
The problem
Manual defect creation strips away the evidence engineers need
Copying an error message rarely preserves the exact run, environment, commit, or artifact behind the failure.
What teams gain
- Create an issue from the failed test
- Include error and run context
- Keep artifacts and source evidence connected
How it works
A clear path from setup to useful evidence.
02
Create
Open the Jira issue flow directly from Testream.
03
Track
Keep the issue and originating test evidence connected during follow-up.
Product proof
Better defect reports with less manual writing
Failure-to-issue workflow
Structured run metadata
Artifact continuity
Jira-native ownership and status
Continue exploring
Related Testream features
Evidence
Failure inspection
Inspect failed tests with errors, stack traces, screenshots, traces, videos, logs, and Jira issue creation in one workflow.
Evidence
Jira run summaries
Show linked automated test runs, status, commit context, and suite changes directly on the Jira issues your team already follows.
Platform
Artifact storage
Keep screenshots, traces, videos, and logs connected to test results while using your own supported storage configuration.