Jira integration

Triage your flaky tests faster by creating automatically assigned and labeled tickets with the Jira integration

When Trunk Flaky Tests detects a flaky test, you can create an automatically generated Jira ticket for your team to pick up and fix the test.

Webhook payloads will also contain ticket information when a Jira ticket is created with the integration or when existing tickets are linked.

Connecting to Jira

To connect a Jira Cloud project, navigate to Settings -> Repositories -> Ticketing Integration and select Jira as your Ticketing System.

Then complete the form and click Connect to Jira Cloud with the following information.

Field Name	Description	Examples
Jira URL	The URL to your Jira Cloud project.	https://trunk-io.atlassian.net
Project Key	The project key for your Jira project.	KAN
Email	The email associated with your Jira API token.	[e-mail]
Jira API token	Create your Jira API token here.	ATATT*****19FNY5Q
Default label(s) for new tickets	Labels applied to new Jira tickets created through Trunk Flaky Tests	flaky-test, debt

After connecting to Jira, you can specify a default issue type for new tickets and a default assignee for new tickets.

API Token permissions

Your Jira user account must have the following project permissions to create a Jira API token that allows Trunk to read, create, and assign tickets automatically:

• Create issues
• Assign issues OR Browse users and groups (global permission)
• Browse projects
  • If issue-level security is configured, issue-level security permissions must be granted to read issues.

You need to create an API token with the following scopes:

• Required scopes (classic)
  • read:jira-work
  • write:jira-work
  • read:jira-user
• Required scopes (granular):
  • read:issue:jira
  • read:issue-meta:jira
  • read:issue-security-level:jira
  • read:issue.vote:jira
  • read:issue.changelog:jira
  • read:avatar:jira
  • read:status:jira
  • read:user:jira
  • read:field-configuration:jira
  • read:application-role:jira
  • read:group:jira
  • read:issue-type:jira
  • read:project:jira
  • read:project.property:jira
  • read:issue-type-hierarchy:jira
  • read:project-category:jira
  • read:project-version:jira
  • read:project.component:jira
  • read:permission:jira
  • write:issue:jira
  • write:comment:jira
  • write:comment.property:jira
  • write:attachment:jira

Jira tokens cannot last longer than 365 days. Once the token expires, you will need to generate a new API token.

Create a new ticket

You can create a new ticket for any test listed in Trunk Flaky Tests.

There are 2 ways to create a new ticket in the Flaky Test dashboard:

• Click on the options menu for any test case on the repo overview dashboard

• Use the Create ticket button in the top left corner of the test case details page.

Before you create the ticket, you will have a preview of the title and description.

Create with Jira

If you are connected to Jira, you can click the Create Jira Ticket button at the end of the modal, which will automatically create a ticket with the configured labels and assignees.

Link existing tickets to tests

If you already have a ticket in Jira that you want to link to a test in the dashboard, you can use the Link Ticket to Test Case API.

Required Custom Fields

Some Jira projects require additional fields beyond the standard fields (like summary, description, and issue type) to be specified when creating tickets. Common required custom fields include:

• Components - Categories or modules within your project
• Affects Version - Which version of your product is impacted
• Fix Version - Target version for the fix
• Epic Link - Parent epic for the ticket
• Sprint - Sprint assignment
• Story Points - Estimation field
• Custom fields specific to your organization

Enterprise Feature

Support for required custom fields is an Enterprise feature.

If your Jira project requires custom fields that aren’t supported in the standard Trunk Flaky Tests integration, you’ll see an error message when attempting to create a ticket:

The Jira project [PROJECT_KEY] requires a field "[field_name]". 
Contact [e-mail] to upgrade your account for custom field support.

To enable support for your required custom fields, contact our sales team at [e-mail] to discuss Enterprise plan options.

Alternative: Remove Field Requirements

If you don’t need Enterprise features, you can modify your Jira project settings to make custom fields optional instead of required. This allows Trunk Flaky Tests to create tickets without needing to specify those fields.

To make a field optional in Jira:

1. Navigate to Project Settings in your Jira project
2. Select Issue Types from the sidebar
3. Choose the issue type you’re using for flaky test tickets (e.g., Task, Bug)
4. Click Fields to see all fields for that issue type
5. Locate the required custom field (e.g., “Components”)
6. Click the field to open its configuration
7. Uncheck Required or change the field requirement setting
8. Save your changes

After making the field optional, you should be able to create tickets through Trunk Flaky Tests without encountering the error.

Note: You may need Jira Administrator permissions to modify project settings. If you don’t have access, contact your Jira administrator to make these changes.