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. Open the Jira tile, then click Connect Jira in the panel. 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, Assignee, Sprint, and Labels as needed. Fields your Jira project requires for that issue type appear below them. Review the Summary and Description, then click Create to file the issue in Jira.For the report format, AI title suggestions, labels, and attachments, see Raise an issue from a failed test.
5

Confirm creation

The panel shows Issue created in Jira, the Jira project, the issue key, and what the issue included. Click Open in Jira to open the issue, or copy its link.

What TestDino Pre-fills

Every issue is created with structured context so the developer receiving it has everything needed to investigate. The Concise report format keeps only the summary, the failure information, and the links. See Choose what the description includes.
Issue titles no longer start with [TestCase]. To find issues raised from TestDino, filter by the TestDino label: labels = TestDino.

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, open the Jira tile and click Disconnect, 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
  • If the button reads No Integration Found, no issue tracker is ready to use. Connect Jira in Settings → Integrations
  • The selected issue type has no labels in your Jira project, or its fields did not load. Close and reopen the panel to try again
  • If the message stays, the issue type has no labels and the issue is created without them. Pick another issue type to add labels
  • 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 October 30, 2026