Skip to main content
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.
WarningAvailable on TestDino Team and Enterprise plans.

​
Prerequisites

  • A TestDino project with test runs uploaded (Getting Started)
  • A Jira Cloud account with View and Update access to the target Jira project
  • A Jira project to file issues into

​
Connect Jira to TestDino

​
Open the Integrations page

Go to Settings → Integrations in your TestDino project. Find the Jira card and click Connect. TestDino Settings → Integrations page showing all issue tracking cards with Connect buttons

​
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. See Permissions for the full list. Atlassian OAuth authorization screen showing TestDino requesting Jira access

​
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. Jira connected configuration in TestDino showing default app, project, and sync/disconnect options
NoteThe default project is a convenience setting. You can select a different project each time you create an issue.

​
Permissions

TestDino does not require Jira Admin. The account you connect needs View and Update access to the Jira projects you file issues into. TestDino acts as the account that authorized the connection and cannot exceed that account’s own Jira permissions. It does not create Jira projects, edit project settings, or change Jira configuration. To restrict access to specific projects, connect with a dedicated Jira account that has View and Update on those projects only.

​
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.
1

Open a Test Run

Navigate to a Test Run in TestDino.
2

Select a test case

Choose a failed or flaky test case from the run.
3

Raise Issue

Click Raise Issue and select Jira.Raise Issue button showing connected issue tracking integrations to select from
4

Configure & Create issue

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.Jira bug report form in TestDino showing prefilled fields and description
5

Confirm creation

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.Jira issue confirmation showing issue key, ID, and link

​
What TestDino Pre-fills

Every issue is created with structured context so the developer receiving it has everything needed to investigate.

​
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
Last modified on September 3, 2026