Jira
Connect DontBreak to Jira and every test failure becomes an issue in your project — complete with the failed steps, error messages, screenshots, and a link back to the full report. When the test passes again, the issue is transitioned to Done automatically. Your bug triage happens in the same project where your team already tracks work, with no copy-pasting.
Connecting Jira
Go to Automation > Projects in the sidebar, where Jira sits alongside Trello and GitHub Issues under Project Management. Select the Jira tab. The quickest way to connect is one-click OAuth — authorize DontBreak on Atlassian and you're redirected straight back, connected. If you'd rather use a scoped API token, there's a manual option below.
Click Connect with Jira
On the Projects page, click Connect with Jira. You're sent to Atlassian's consent screen.
Authorize on Atlassian
Review the access DontBreak requests — reading and writing your Jira work items, plus offline access so it can keep the connection alive — and approve it. If your Atlassian account has access to more than one Jira site, DontBreak uses the first one.
You're connected
Atlassian redirects you back to the Projects page, now connected, ready to choose a project. DontBreak refreshes the authorization automatically in the background, so you won't have to reconnect on a schedule.
Or connect manually with an API token
If an Atlassian admin has restricted third-party OAuth app authorizations, or you'd simply prefer a scoped token, toggle Or connect manually with an API token on the Projects page to reveal the site URL, email, and token form.
Create an API token
Open id.atlassian.com/manage-profile/security/api-tokens in Atlassian, click Create API token, give it a label like "DontBreak", and copy the token. You'll only see it once, so paste it somewhere safe before leaving the page.
Enter your site URL, email, and token
Fill in your Jira site URL (https://yourteam.atlassian.net), the email of your Atlassian account, and the API token you just created. DontBreak stores the token encrypted.
Connect
Click Connect. DontBreak validates the three fields against Jira before saving — if the site URL, email, or token is wrong, you'll see an error and nothing is stored. On success you're connected and can choose a project.
Choosing a project and issue type
Once connected, pick where failures should land:
Choose a Project
Select the Project for new issues from the dropdown. It lists the projects your Atlassian account can access.
Choose an Issue Type
Pick the Issue Type DontBreak creates — for example Bug or Task. The dropdown lists the standard issue types for the selected project; subtask types are excluded, since a failure issue can't be created as a subtask.
Save and test
Click Save Configuration, then Test Connection to confirm DontBreak can reach your Jira site and the selected project. You'll see "Connection successful!" if everything is wired up.
What gets created on failure
When a test fails, DontBreak creates an issue in your configured project using your chosen issue type:
- Summary:
[FAIL] Test name — browser device, so you can see at a glance what broke and where (e.g. which of your browsers and devices). - Description: the test name and URL, browser, device, and run time, followed by each failed step with its error message, and a View Full Report link to the run in DontBreak.
- Attachments: screenshots captured at each failed step, uploaded as real Jira attachments so you can see exactly what the page looked like.
No duplicate issues
DontBreak keeps one open issue per test. If the same test fails again while its issue is still open, the existing issue is kept and updated to point at the latest run instead of cluttering your project with duplicates.
When the previously failing test passes again, DontBreak transitions the open issue to your project's Done status automatically — your board reflects the real state of your tests without anyone triaging by hand.
How auto-resolve picks the Done status
DontBreak transitions the issue using the first available transition whose status category is Done — not a status matched by name, so a custom "Done"-category status works too. If your workflow has no transition into a Done-category status from the issue's current state, DontBreak leaves the issue as-is rather than guessing. Make sure the issue type's workflow offers a path to a Done-category status if you want auto-resolve to fire.
Testing the connection
Use the Test Connection button on the Projects page any time to confirm DontBreak can still reach your Jira site and the selected project. It's the quickest way to check the integration is healthy — much better to catch a problem now than to discover a real failure never got filed.
Disconnecting
At the bottom of the Projects page, click Disconnect. This removes the stored credentials and stops issue creation immediately. Existing issues stay in your project — DontBreak never deletes them. You can reconnect any time from the same page.
Warning
If the authorization is revoked or expires (rather than disconnecting here), the integration disables itself automatically the next time it can't reach Jira. Reconnect from the Projects page — click Connect with Jira to re-authorize, or paste a fresh API token via the manual option — to re-enable it.
Troubleshooting
- Issues stopped being created. The authorization was most likely revoked or expired, which disables the integration automatically. On the Projects page, click Connect with Jira to re-authorize via OAuth — or, if you connected manually, create a fresh token at id.atlassian.com/manage-profile/security/api-tokens and reconnect with your site URL, email, and the new token.
- The configured project was archived or deleted. Open the Projects page, pick a project again from the Project dropdown, choose an issue type, and click Save Configuration. Run Test Connection to confirm the new selection works.
- The configured issue type was removed. If the issue type no longer exists in the project, re-open the Issue Type dropdown, pick an available type, and save.
- The issue was created but isn't on your board. In Scrum projects, new issues land in the Backlog, not the active sprint board. Check the Backlog view in Jira's sidebar, or adjust your board filter if you want them visible immediately.
- You deleted or manually closed a DontBreak issue in Jira. No problem — DontBreak checks the issue before reusing it, so the next failure of that test opens a fresh one.
- Passing tests aren't being resolved. Auto-resolve only fires when the issue type's workflow has a transition into a Done-category status from the issue's current state. Check the workflow in Jira and add a transition to a Done-category status if one is missing.
Works well with
- Slack — get the instant alert in chat while the Jira issue tracks the fix.
- Understanding test results — what you'll find behind the issue's report link.
- Scheduling — scheduled runs plus Jira means overnight failures are already filed in your project by morning.