Issue Tracking
Automatically create Jira tickets when Playwright tests fail — with evidence pre-filled
Tynkr creates Jira issues automatically when a workflow fails, with the failure summary, root cause analysis, affected test name, screenshots, and execution log attached. No copy-pasting from CI output. You define the project, issue type, and labels once — Tynkr handles the rest on every failure.
What you can do
- Create a Jira bug automatically when a critical user journey test fails
- Link test failures to the current sprint so QA work is visible in planning
- Attach execution screenshots and logs to the Jira issue without manual steps
- Deduplicate: only open a new ticket if the failure is not already tracked
Common questions
How does Tynkr create Jira tickets from Playwright test failures?
Tynkr connects to Jira via API token. When a workflow step fails and Jira is enabled, Tynkr creates an issue in the configured project with the failure summary, root cause, test name, and attaches screenshots and execution logs automatically. You configure the issue type, priority, and labels once per workflow.
Can Tynkr avoid creating duplicate Jira tickets for the same failure?
Yes. Tynkr checks for open issues with matching failure signatures before creating a new ticket. If a matching open issue exists, it adds a comment with the new execution details instead of creating a duplicate.