Skip to main content
Jira integration enables automatic bug filing for failures that Bugzy triages as product bugs. When tests fail and Bugzy determines the failure is a genuine product issue (not a test flake or environment problem), it creates a Jira issue with full reproduction details.

​
What Jira enables

  • Automatic bug filing — Triaged product failures are filed as Jira issues without manual intervention
  • Duplicate detection — Bugzy checks existing Jira issues before creating new ones to avoid duplicates
  • Rich bug reports — Issues include reproduction steps, error details, screenshots, and environment info
  • Status-based triggers — Jira status changes (e.g., “Ready for QA”) can trigger the verify-changes task

​
Setup

1

Navigate to connections

Go to Dashboard > Projects > [Your Project] > Connections.
2

Connect Jira

Click Connect Jira. This opens the Jira OAuth flow managed by Nango. Supports Jira Cloud.
3

Authorize access

Select your Atlassian site and authorize the requested permissions.
4

Configure project mapping

After connecting, map your Bugzy project to the target Jira project where bugs should be filed.

​
How bug filing works

The bug filing flow is part of the run-tests and triage-results tasks:
  1. Test execution — Bugzy runs tests and collects results
  2. Triage — Bugzy analyzes failures, categorizing each as: product bug, test issue, or environment problem
  3. Duplicate check — For product bugs, agent searches existing Jira issues to avoid duplicates
  4. File issue — If no duplicate exists, agent creates a Jira issue with structured details
  5. Notify team — If Slack/Teams is connected, the team is notified about the new issue

​
Bug report contents

Each filed Jira issue includes:
FieldContent
SummaryConcise description of the failure
DescriptionDetailed reproduction steps
Error detailsStack traces, error messages, assertion failures
ScreenshotsCaptured during test execution
EnvironmentBrowser, OS, app version, test URL
Labelsbugzy-automated, test case ID
PriorityBased on failure severity and impact

​
Duplicate detection

Before creating a new issue, Bugzy:
  1. Searches the Jira project for issues with similar summaries
  2. Checks for matching error signatures in existing issues
  3. If a likely duplicate is found, adds a comment to the existing issue instead of creating a new one
  4. Links related issues when multiple test failures stem from the same root cause

​
Event processing

Jira can also send events back to Bugzy:
Jira eventBugzy action
Issue moved to “Ready for QA”Triggers verify-changes task to re-run relevant tests
Issue resolved/closedBugzy marks related findings as addressed
Configure Jira event processing in Dashboard > Event Triggers.

​
Jira Server (on-premises)

For Jira Server or Data Center deployments behind a firewall, Bugzy supports secure access via MCP Tunnel:
  • MCP Tunnel uses Ably for real-time communication between Bugzy’s cloud infrastructure and your on-premises Jira instance
  • No inbound firewall rules required — the tunnel initiates an outbound connection from your network
  • Configure on-prem access in Dashboard > Connections > Jira > Advanced
Jira Cloud connects directly via OAuth. Jira Server requires the MCP Tunnel agent installed in your network. Contact support for setup assistance.

​
Also supported

Looking for a different issue tracker? Bugzy also supports Azure DevOps, Asana, and Linear — each following the same triage-and-file pattern described above.

​
Troubleshooting

Issues not being created — Verify the Jira connection is active and the project mapping is configured. Check that the connected Jira user has permission to create issues in the target project. Duplicate issues being filed — The agent uses title and error signature matching for duplicate detection. If you see duplicates, ensure the Jira project field mapping is correct. “Forbidden” errors — The OAuth token may lack required permissions. Disconnect and reconnect Jira from the project connections page to re-authorize.