Thunders and Jira & Confluence talk to each other in both directions.
Way 1 — Thunders → Jira: when a test fails, you don't need to jump into Jira, open a new work item, and manually copy over what went wrong. Thunders AI can create that ticket for you, right from the failed run, with the context already attached.
Way 2 — Jira & Confluence → Thunders: already have your requirements written up as Jira work items or Confluence pages? Point Thunders AI at one, and it'll use it as a knowledge base to generate test plans and test cases for you.
Prerequisites
Before you can report bugs to Jira, you'll need:
An Atlassian account, with access to the Jira project you want bugs reported into. This is where your work items will land, so make sure it's one you actually have permission to create issues in.
Connect Jira & Confluence
Both ways below share the same one-time setup: connecting your Atlassian account to Thunders, per project.
An important thing to know: connections in Thunders are personal and per project — there are no more shared, org-wide tokens. This means every teammate who wants to use Jira & Confluence, in either direction, needs to connect their own account.
There are two equally valid ways to get to the connection dialog, depending on where you happen to be in the app:
Option A — From Thunders AI
Go to the Thunders AI tab.
Click the 🧠 brain icon — this opens the connectors list.
Click + Add connector.
Select Jira & Confluence from the list of available integrations.
Option B — From the Connectors tab
Go to the Connectors tab.
Look for Jira & Confluence in the list of integrations.
Click Connect.
Both paths lead to the same place: a connection dialog where you choose how to authenticate.
Choose how to authenticate
Unlike our other integrations, Jira & Confluence support two ways to connect. Pick whichever fits your setup — both finish the connection just as well.
Option 1: Sign in with OAuth
In the dialog, select Sign in.
Authenticate with your Atlassian account when prompted.
Approve the requested permissions.
Option 2: Use an API token
In the dialog, select API token.
If you don't already have one, generate a token from your Atlassian account settings.
Paste the token into the field, along with any other details the dialog asks for (site URL, email).
Click Add connector.
Use OAuth if you want the fastest setup with a simple login prompt. Use an API token if your organization requires scoped, revocable credentials, or you're connecting a service account rather than a personal login.
Way 1: Thunders → Jira — Report a bug
Once Jira is connected, reporting a bug takes just a few clicks:
Go to the failed run you want to report on.
Click the bug icon next to the failed step.
Click Report bug.
Select Jira as the integration you want to send this bug to.
In the Guidance field, write a short, natural-language prompt describing your ticket preferences — for example, which project it should go into, the issue type, who should be assigned, or anything else relevant. You don't need to fill out a rigid form; just describe what you want in plain language.
Click Send.
Thunders AI takes it from there. If anything important is missing to create the ticket — say, which Jira project to use — it will ask you directly in chat. Just answer, and it continues.
Once everything is in place, the ticket is created successfully in Jira, and Thunders AI will let you know it's done.
Way 2: Jira & Confluence → Thunders — Build test plans and test cases from a work item or page
Already have your requirements captured in Jira or Confluence? You can use that work item or page as a knowledge base and have Thunders AI generate test plans and test cases from it — no retyping required.
Make sure Jira & Confluence is enabled as a connector in your Thunders AI chat (see Connect Jira & Confluence above).
In the chat, reference the Jira work item or Confluence page you want to use — a title, an issue key/page ID, or a link all work.
Ask Thunders AI to build a test plan or test cases from it, for example: "create test cases from PROJ-123" or "turn this Confluence page into a test plan: ".
Thunders AI reads the work item or page and drafts the test plan or test cases for you to review and refine.
Good to know
This exact same flow also works for accessibility reports: no separate process to learn.
The steps above are the same for every other integration Thunders supports: Linear, ClickUp, Notion, Shortcut, Azure DevOps, or even a custom integration you've added yourself. What changes from one integration to another is mainly what you mention in your Guidance prompt (a team for Linear, a project for Jira, a list for ClickUp, and so on): the connection steps and the reporting flow itself stay the same.
Way 2 works with any Jira work item or Confluence page you have access to — just give Thunders AI the title, ID, or link, and it pulls the rest itself.