Automatic ticketing
With a connected Linear, Jira, or Asana integration, Trunk can manage ticket lifecycle automatically: create a ticket when a test becomes flaky or broken, reopen it if a fixed test regresses, and close it when the test returns to healthy. See Automatic ticketing for setup and behavior.Ticket content
Flaky Tests automatically generates tickets complete with a title and description. If you’re connected to Linear, Jira, or Asana, you can also assign default issue types, teams, projects, or assignees. The ticket description contains the following information:- Identifier of the test
- Since when has the test been labeled flaky
- The last time this test failed
- The impact when run on PRs
- The impact when run on branches
- Quarantine status
- Most common failure reasons
- Code owners, according to the CODEOWNERS file in your repository
Ticket event history
When you unlink a ticket and re-link a test case to a different ticket, all events from the previous ticket association are preserved. The test case’s Events tab shows the full history — creation, updates, and status changes — across all tickets the test has ever been linked to, not just the current one.Integration setup
Ticket Creation supports integrations with Linear, Jira, and Asana. For any other platform, the generated ticket content is formatted in Markdown and can be copied across — see Other ticketing platforms.
Linear
Jira
