> ## Documentation Index
> Fetch the complete documentation index at: https://docs.testdino.com/llms.txt
> Use this file to discover all available pages before exploring further.
# Jira Integration for Playwright Failures
> Create Jira issues from failed or flaky Playwright tests in TestDino.
export const VideoSchema = ({name, description, thumbnailUrl, uploadDate, duration, contentUrl, embedUrl}) => {
const schema = {
"@context": "https://schema.org",
"@type": "VideoObject",
name,
description,
thumbnailUrl,
uploadDate,
...duration ? {
duration
} : {},
...contentUrl ? {
contentUrl
} : {},
...embedUrl ? {
embedUrl
} : {},
publisher: {
"@type": "Organization",
name: "TestDino",
logo: {
"@type": "ImageObject",
url: "https://docs.testdino.com/logo/light.svg"
}
}
};
return ;
};
The Jira integration creates prefilled bug reports in Jira directly from failed or flaky tests in TestDino. Each issue includes the test name, error details, failure history, console output, screenshots, and links to the TestDino run and Git commit.
This is a **user-level** integration. Each team member connects their own Jira account and creates issues under their own identity.
To see the test cases, runs, and sessions you link here inside the Jira issue view, install the [Jira Forge App](/integrations/issue-tracking/jira-forge-app).
**Warning**
Available on TestDino **Team** and **Enterprise** plans.
## Prerequisites
* A TestDino project with test runs uploaded ([Getting Started](/getting-started))
* A Jira Cloud account with permission to create issues
* A Jira project to file issues into
## Connect Jira to TestDino
### 1. Open the Integrations page
Go to **Settings → Integrations** in your TestDino project. Find the **Jira** card and click **Connect**.
### 2. Authorize your Jira account
TestDino redirects you to Atlassian to authorize access. Sign in to your Jira account and approve the request. TestDino requests permission to read and create issues in your Jira projects.
### 3. Configure defaults
After authorization, select the default **Jira App** (your Atlassian site) and **Project** where issues will be created. You can change these per issue when creating a bug report.
**Note**
The default project is a convenience setting. You can select a different project each time you create an issue.
## Create a Jira Bug Report
Create Jira issues directly from failed or flaky test cases. Each issue includes test metadata, so your team has full context without opening separate reports.
Navigate to a **Test Run** in TestDino.
Choose a failed or flaky **test case** from the run.
Click **Raise Issue** and select **Jira**.
Select the **Project** and **Issue Type** (Bug, Task, etc.). Set **Priority**, **Labels**, **Assignee**, **Reporter**, and **Sprint** as needed. Review the **Summary** and **Description** (auto-generated from failure data). Click **Create** to file the issue in Jira.
TestDino shows a confirmation with the Jira issue key, internal ID, and a copyable URL. Click **View in Jira** to open the issue directly in Jira.
The issue appears in your Jira project with all the prefilled fields and description content intact.
## What TestDino Pre-fills
Every issue is created with structured context so the developer receiving it has everything needed to investigate.
| Section | Field | Pre-filled Content |
| :-------------- | :------------------ | :------------------------------------------------------------------------------------------------------ |
| **Jira Fields** | Project | Jira project for the ticket |
| | Issue Type | Bug, Task, or any type your Jira allows |
| | Priority | Impact level for triage |
| | Labels | Team or component tags |
| | Assignee | Routing field for the responsible owner |
| | Reporter | Routing field for the reporting user |
| | Sprint | Planning field for the active sprint |
| | Dates and Points | Optional start date, due date, and estimate points |
| | Summary | `[TestCase] - ` |
| **Description** | Test Details | Test name, file, branch, commit author/message, environment, run ID, execution date, duration, attempts |
| | Failure Information | Error type and key error message |
| | Focused Steps | Failing attempt with a code frame |
| | Links | TestDino run, Git commit, CI job |
| | Screenshots | Listed thumbnails; attach more if needed |
| **System Note** | Origin | The issue was generated from an automated test failure |
## Troubleshooting
* Click **Sync** on the Jira card in **Settings → Integrations** to refresh projects and fields from Jira
* Verify your Jira account has access to the project you expect to see
* TestDino automatically refreshes OAuth tokens when supported by the provider. If you still see authorization errors, click **Disconnect** on the Jira card, then reconnect and re-authorize
* Ensure your Atlassian account has permission to create issues in the target project
* The button appears on failed or flaky test cases inside a test run detail view. Open a test run and click into a specific failed test
* Verify the Jira integration is connected for your account in **Settings → Integrations**
* Some Jira fields (Sprint, Story Points, custom fields) depend on your Jira project configuration. Verify the field exists and is available for the selected issue type
* Run **Sync** to pull the latest field definitions from Jira
### 2. Authorize your Jira account
TestDino redirects you to Atlassian to authorize access. Sign in to your Jira account and approve the request. TestDino requests permission to read and create issues in your Jira projects.
### 3. Configure defaults
After authorization, select the default **Jira App** (your Atlassian site) and **Project** where issues will be created. You can change these per issue when creating a bug report.
