Jira x Thunders

Keep requirements and test coverage connected. Turn Jira tickets into tests with Thunders AI, report bugs back from failed steps in one click, and sync results to your issues. The loop between what should work and what actually works stays closed.

Close the loop between Jira tickets and test coverage

Turn Jira tickets into accurate, QA-ready tests with Thunders AI.

Report bugs to Jira in one click with screenshots, expected vs. actual, and the execution path.

Sync test results back to Jira. Thunders AI updates the original ticket so anyone reviewing the issue sees what passed and what did not.

How to set up Jira with Thunders

Step 1: Connect your Jira workspace

‍

Go to Knowledge > All sources. Connect your Atlassian account. Thunders gets access to your workspace. For bug reporting, you choose which project the bug lands in.

Thunders Knowledge page, All Sources tab, listing available sources such as Notion, Jira, Linear, Azure DevOps, ClickUp and Shortcut, each with a Connect button

Step 2: Turn Jira tickets into tests

‍

Open Thunders AI. Paste a Jira ticket URL or reference the issue ID. Thunders AI reads the description and acceptance criteria, and because it knows your existing tests and project context, it generates accurate test steps with the right validations.

Thunders AI prompt box with the request “Create a test case based on the acceptance criteria in this Jira ticket PRO-34”, one Jira source attached and Test Case mode selected

Step 3: Run tests and sync results

‍

Execute the generated tests. Thunders AI syncs results back to the Jira ticket. Failed steps include links to the full execution report.

‍

Jira ticket KAN-1 whose description lists the feature, the authentication setup and the environment variables Thunders uses to write the test

Step 4: Report a bug from a failed step

‍

When a test step fails, click 'Report Bug.' Thunders creates a new Jira issue pre-filled with the failure context: step description, expected vs. actual, screenshot, and execution link.

‍

Failed Thunders test run with the Report Bug panel open on a failed step, showing the element, expected and actual behaviour, and a Create a Ticket menu set to Jira ticket

Step 5: Navigate between Thunders and Jira

‍

Every reported bug links to the test and the run it came from. Jump from the Jira issue back to the exact failure in Thunders. Fix the code, re-run the test, and close the loop.

‍

Thunders test run page with a Reported Bugs popover linking the failed step to Jira issue KAN-22

Ready to ship faster with smarter testing?

Screenshot of the Thunders app Test Cases list, showing test sets, labels and last run status, with a label picker open