Jira Cloud Integration

TestOwl integrates with Atlassian Jira Cloud to streamline defect triage. Instead of manually copying step errors, formatting stack traces, and uploading screenshots, QA engineers and developers can file or comment on Jira tickets directly from Run Reports in a 3-step triage wizard.

How the Jira Connection Works

TestOwl connects to Jira Cloud via official Atlassian OAuth 2.0:

• Zero Stored Passwords: Connecting is handled entirely on Atlassian's secure consent screen. TestOwl never asks for or stores Atlassian passwords or API tokens.
• Project-Level Connection: A Project Administrator connects the organization's Jira Cloud site (e.g., your-team.atlassian.net) once for the project.
• Personal Member Link: Individual team members can also connect their own personal Jira identity from within TestOwl. This allows 1-click "Assign to me" and ensures created tickets reflect the author's real Atlassian user profile.
• Data Protection: Before any data is transmitted to Jira, TestOwl automatically removes Secret values, masking-rule matches, and sensitive credential patterns.

Connecting Jira Cloud

1. 1
   In TestOwl, navigate to Project Settings → Integrations → Jira.
2. 2
   Click Connect Jira Cloud.
3. 3
   You are redirected to Atlassian's OAuth consent screen. Sign in to your Atlassian account and select the Jira site you want to connect.
4. 4
   Review the requested permissions and click Accept.
5. 5
   Once returned to TestOwl, configure the project settings:
   • Allowed Projects: Select which Jira projects TestOwl is allowed to create tickets in (supports multi-select, search, and pagination).
   • Default Project & Issue Type: Set the default project key and issue type (e.g., Bug, Defect, or Task).
   • Attach Screenshots: Toggle whether failure screenshots (pre-run and post-run DOM captures) can be attached to tickets.

Filing Defects from Run Reports

When reviewing a failed run in the Run Report (/runs/:runId):

1. Selecting Failures

• Click the Jira Toggle in the test case header.
• Testers can click Select Failed Steps to instantly tick all broken steps, check individual steps manually, or select the entire test case.
• The floating Jira Send Bar at the bottom of the screen displays the count of selected items. Click Send to Jira to open the triage drawer.

2. The 3-Step Triage Wizard

The Jira Triage Drawer guides you through three steps:

Step 1: Options

• Grouping:
  • Single Ticket: Combines all selected failed steps into one comprehensive issue.
  • Ticket Per Item: Creates a separate Jira issue for each selected failed step or test case.
• Evidence Level:
  • Steps and Report Link: Pre-populates the error message, step sequence, expected vs. actual values, locator details, and deep link.
  • Report Link Only: Includes a clean direct link back to the TestOwl run report.
• Sub-tasks: Check this option to create one sub-task per selected step under a single parent ticket.
• Notes: Add custom tester observations to include in the ticket body.

Step 2: Review & Edit

• Action:
  • Create New Issue: File a brand new Jira ticket.
  • Add to Existing Issue: Append execution evidence as a comment onto an existing Jira ticket key (e.g., PROJ-1234).
• Ticket Fields: Edit Summary and Description (formatted in Markdown), Project Key, Issue Type, Priority, Assignee (including 1-click Assign to me), and Labels.
• Custom Fields: TestOwl automatically queries your Jira project schema and renders dynamic custom fields (select, multi-select, text, date, datetime, user picker).
• Attachments: If screenshot attachments are enabled by the admin, choose whether to include pre-run and post-run DOM screenshots.

Step 3: Results

• Review created and updated Jira issue keys (e.g., QA-42). Click any issue key to open it directly in Atlassian Jira Cloud.

Bi-Directional Status Tracking

Once a Jira issue is created or linked:

• Linked Ticket Chips: A Jira ticket badge appears directly on the test case header and on each associated step status pill in the Run Report.
• Live Status Categories: The chip shows the ticket's current Jira status category (e.g., To Do, In Progress, Done).
• Refresh Links: Click the Refresh button on the report header to pull the latest status directly from Jira without reloading the page.