Jira Integration

Connect with Atlassian

This is the quickest way to connect a Jira Cloud site. Go to Members > Integrations and click Jira, then click Connect with Atlassian.

You will be redirected to Atlassian to approve TestingBot. We request read and write access to Jira work items, so we can read your projects and issue types and create issues, plus offline access so we can keep creating issues without asking you to sign in again. We never see your password, and you can revoke access at any time from your Atlassian account settings. TestingBot does not store your Atlassian account details.

Once connected, the page shows the connected site and a Test connection button you can use to confirm everything works.

Choose a Jira site

If your Atlassian login has access to more than one Jira site, TestingBot asks which site it should create issues in right after you approve the connection. Pick the site and click Use this site. If you only have one site, this step is skipped. You can switch sites later by disconnecting and connecting again.

Use an API token

Prefer a token, or running Jira Server or Data Center, which does not support the Atlassian OAuth flow? On the Jira integration page, open Use an API token instead and fill in the Jira email you sign in with, an API token, and the Atlassian host of your Jira instance (for example https://yourcompany.atlassian.net/).

Jira Cloud no longer accepts account passwords for REST API access. Generate an API token from Atlassian, Security, API tokens and use that instead. Jira Server and Data Center users can supply a Personal Access Token (PAT) in the same field. We store these credentials encrypted and only use them to create issues on your behalf.

Report a bug

Once Jira is connected, you can create an issue from any automated test. Open the test from the Test Detail page, click the Report a bug button in the header and choose Jira.

A form appears where you pick the Project and Issue type, then fill in the Title and Description. The issue type list updates to match the project you select. The description is pre-filled with the test metadata, including the test URL, environment, name and result.

You can also choose which test artifacts to attach: the console and driver logs, the network log (HAR) and the video recording. Attachments are added to the issue in the background.

Click Create issue. The Jira ticket is created in your Jira instance and TestingBot shows a link to view it in Jira.

What gets included

The pre-filled description contains a metadata block with:

• The test URL, which opens a shareable test page with the video, screenshots and logs
• The environment the test ran on, the browser or device and the operating system
• The test name
• The test result (passed or failed)

You can edit or remove any of this before submitting. Whoever opens the issue in Jira can follow the test link to watch the video and inspect the logs, without needing a TestingBot account. When you tick the artifact checkboxes, the logs, the network log and the video are uploaded to the issue as attachments.

Live Testing

During a manual Live Testing session, click Report Bug to take a screenshot and annotate it in the editor. Then click Report a bug and choose Jira.

The same issue form appears, and the annotated screenshot is attached to the issue you create, together with the session metadata.

Disconnect

To disconnect Jira, go to the Jira integration page and click Remove Jira integration, then confirm.

Issues that were already created in Jira are not affected. You can reconnect at any time, with the same or another Jira account, and with Atlassian OAuth or an API token.