Jira Integration
Sync test findings directly to your Jira backlog. Auto-create tickets, keep statuses in sync, and give your team full context — repro steps, screenshots, and AI fix suggestions.
SETUP GUIDE
Connect in 4 steps
Authenticate via OAuth
Navigate to your project settings, select Integrations → Jira, and click Connect. TestOptim uses OAuth 2.0 to securely authenticate with your Atlassian account — no passwords or API tokens stored.
You'll be prompted to select which Atlassian site and project to connect. TestOptim requests only the permissions it needs: create issues, read issue data, and update issue status. You can revoke access at any time from your Atlassian account settings.
Bi-directional issue sync
Once connected, TestOptim syncs issue status in both directions. When a test failure creates an issue in TestOptim, it appears in Jira. When your team updates the status in Jira (e.g., In Progress, Done), it syncs back to TestOptim.
Status mapping is configurable per project. You can define which Jira statuses correspond to TestOptim's issue states (Open, Acknowledged, In Progress, Resolved, Closed). The sync runs every few minutes with no manual intervention needed.
Auto-create tickets from failures
Every test failure can automatically generate a Jira ticket — complete with the issue title, severity, repro steps, screenshots, console logs, and an AI-generated fix suggestion. Your QA team never misses a finding.
You control which severity levels trigger auto-creation. For example, configure HIGH severity issues to create tickets immediately, MEDIUM to batch into a daily summary, and LOW to skip. You can also set a cooldown period to prevent duplicate tickets for the same issue.
Link existing issues to findings
TestOptim can scan your Jira backlog and link existing tickets to related exploration findings. When a test run surfaces an issue that matches an existing ticket, TestOptim links them so your team has full context.
Matching is done by title similarity and component mapping. You can review and confirm suggested links before they're created. This keeps your Jira board clean and avoids duplicate work.
WHY CONNECT