Jira

Connect ContextQA to Jira to generate test cases from tickets, report defects with AI root cause analysis, and sync test execution status bidirectionally.

Quick answer

Connect ContextQA to Jira to generate test cases from tickets, report defects with AI root cause analysis, and sync test execution status bidirectionally. Use this page to understand when the capability applies, complete its user-facing workflow, and verify the expected result.

What this page covers

Who is this for? SDETs, developers, and engineering managers who want to generate tests from Jira tickets and report defects directly from ContextQA test failures.

The ContextQA Jira integration creates a two-way connection between your requirements and your test suite. You can generate test cases directly from a Jira user story, view live execution status inside Jira, and report defects as Jira issues without leaving the test result page.

Watch the Jira-to-tests walkthrough.

Business use case: Generate tests from the Jira stories selected for a release so QA can preserve source traceability, review the proposed coverage, and run accepted tests without copying ticket content into a separate document.

Interactive demo: generate tests from Jira

Use this guided walkthrough to see how a Jira work item becomes traceable test coverage in ContextQA. Follow the pointer through the Jira selection and generation workflow, then use the instructions below when you configure your own connection.

What to notice

The Jira ticket remains the source context for the generated tests.
Review gates let a tester refine proposed coverage before accepting it.
Traceability connects delivery work, test execution, and failure follow-up.

Set up the Jira integration

Open Integrations & Plugins in the left navigation.
Find Jira in All Plugins or Bug Reporting and select View Details.
Open Config when you need to create or change the connection.
Enter the Jira Account URL, such as https://yourorg.atlassian.net.
Enter the Jira account User Name (normally the email address used for Jira Cloud).
Create a Jira API token at Atlassian account security, then enter it as the API Key.
Save the integration and confirm that its Jira details are displayed.

Treat the Jira API token as a secret. Never include it in screenshots, examples, ticket descriptions, or test steps.

Generating Tests from Jira Tickets

Open Requirements.
Select Upload Jira Requirement.
Continue to the Jira ticket picker.
Search by ticket key or text and select one or more tickets that belong to the same testing objective.
Continue and review the detected variables. Mark sensitive values as secrets where appropriate.
Answer any clarification questions required to remove ambiguity from the selected stories.
Start generation and leave the requirements page open or return later while ContextQA processes the selection.
Open the generated requirement record and review each proposed test. Edit it if needed, then accept or reject it.
Run an accepted test once and review its steps and evidence before promoting it to a shared suite or plan.

The selected Jira item remains the source requirement, which makes it easier to explain why the test exists and which delivery item it covers.

Running Tests from Jira

With test cases linked to a Jira ticket, you can trigger execution from the ContextQA panel inside Jira:

Open the Jira ticket
In the ContextQA panel, find the linked test cases
Click Execute next to the test case you want to run, or Execute All to run all linked tests
The panel updates with a status indicator (Running → Passed / Failed) as the execution progresses

You can also run tests from ContextQA directly and the results will be visible in the Jira panel the next time you open the ticket.

Auto-Creating Defects from Test Failures

When a test case fails and the failure indicates a genuine application bug, ContextQA can create a Jira issue automatically with all relevant evidence attached.

Interactive demo: report a failure to Jira

Follow the failure-to-defect workflow to see how ContextQA carries test identity, root-cause context, reproduction information, and evidence into a Jira issue for review.

What to notice

The failed execution remains the evidence source for the Jira issue.
A reviewer can confirm the project, issue type, summary, and description before submission.
The resulting issue link preserves traceability between triage, delivery work, and the ContextQA result.

Via the UI

Open the failed test execution report in ContextQA
Click the Create Bug button (or JIRA button in the failure reporting toolbar)
Select the Jira project and issue type (Bug is the default)
Optionally customize the summary and description
Click Create Issue

ContextQA creates the Jira issue and populates it with:

Summary: Derived from the test case name and the failing step
Description: AI-generated root cause explanation, reproduction steps, and the exact step that failed
Attachment: The failure screenshot
Links: A direct URL to the ContextQA execution (for video, trace, and full step log access)
Labels: The test case label (Jira ticket ID) for traceability

A link to the newly created issue appears immediately in the ContextQA execution report.

Automatic bug creation and sync status

When automatic Jira bug creation is enabled, ContextQA creates a Jira issue automatically when a test run fails. The status of this auto-creation is visible directly on the execution screens:

Auto-created bug badge: When ContextQA successfully creates a Jira issue for a failed run, a clickable badge appears in the execution header displaying the Jira issue key (e.g., MYAPP-1234). Click the badge to open the issue directly in Jira.

Sync status banner: If the automatic bug creation fails (for example, due to invalid field values or permission issues), a warning banner appears at the bottom of the live execution screen and the run results screen. The banner displays the specific error reason (e.g., "labels: The label 'AI Upload' can't contain spaces.") and a Retry button. Click Retry to attempt the Jira issue creation again. The banner disappears when the sync succeeds or when the issue is created manually.

The sync status banner only appears when the auto-creation pipeline fails. It does not appear for successful syncs, pending syncs, or legacy runs that predate this feature.

Via MCP

create_defect_ticket(
    execution_id="27045",
    project_id="MYAPP"
)
# Returns: {"ticket_id": "MYAPP-1234", "url": "https://yourorg.atlassian.net/browse/MYAPP-1234"}

This is the recommended approach for automated triage pipelines. Combine it with get_execution_status and get_root_cause to build a workflow that creates a Jira bug only when a failure persists across multiple runs:

# Run the test
execution = execute_test_case(test_case_id="1234")
status = poll_until_complete(execution)

if status["result"] == "FAILED":
    # Get AI root cause before creating the ticket
    root_cause = get_root_cause(execution_id=status["execution_id"])

    # Create the defect ticket
    ticket = create_defect_ticket(
        execution_id=status["execution_id"],
        project_id="MYAPP"
    )
    print(f"Defect created: {ticket['url']}")

Viewing Test Coverage in Jira

The ContextQA panel in Jira shows a summary of test coverage for each ticket:

Test Cases Linked: How many test cases have been generated for or linked to this ticket
Last Execution Status: The most recent execution result for each linked test case
Coverage Percentage: What fraction of the acceptance criteria have corresponding test cases

This view gives product managers and developers visibility into test health without leaving their workflow in Jira.

Bidirectional Status Sync

When you configure the integration with write access to Jira:

When all test cases for a Jira ticket pass, ContextQA can automatically transition the ticket to a configured status (e.g., Ready for Release or Done)
When a test case fails, ContextQA can reopen the linked ticket or add a comment with the failure details
Configure these options from Integrations & Plugins → Bug Reporting → Jira → View Details → Config when they are enabled for your workspace.

Filtering Tests by Jira Ticket

In the ContextQA Test Cases view, use the Labels filter to display only test cases linked to a specific Jira ticket. Labels are applied automatically during generation and follow the Jira ticket number format (e.g., MYAPP-123).

Using the Azure DevOps Integration

If your team uses Azure DevOps (ADO) instead of Jira, the integration follows the same patterns. Navigate to Integrations & Plugins → Bug Reporting → Azure DevOps → View Details → Config and configure your ADO organization URL and personal access token. The create_defect_ticket MCP tool supports ADO by setting the tracker parameter accordingly.

See the Azure DevOps Integration page for full ADO-specific configuration details.

Troubleshooting

"Cannot connect to Jira" error during setup:

Verify the base URL does not have a trailing slash
For Jira Cloud, the URL format is https://yourorg.atlassian.net (not .com)
Confirm the API token is for the same account as the email address entered
If you are on Jira Server, ensure the ContextQA server can reach the Jira URL (firewall/VPN)

An "invalid JSON" or unexpected login-response error appears:

This usually means Jira returned an HTML sign-in page, redirect, proxy page, or gateway error where the integration expected JSON. Open Integrations & Plugins → Bug Reporting → Jira → View Details → Config, then reconnect and verify the account URL, account email, API token, network reachability, and Jira permissions. For Jira Cloud, use the tenant base URL without a trailing slash. Do not paste the token or full response body into a ticket or shared log; if the error continues, provide a redacted timestamp and ContextQA run or request reference to support.

Test cases not appearing in the Jira panel:

Ensure the ticket ID format matches exactly (case-sensitive: MYAPP-123 not myapp-123)
Confirm the integration is configured from both sides (ContextQA settings and Jira panel installation)

Defect tickets missing screenshots:

Screenshots are attached as links, not as uploaded files, due to Jira attachment size limits
Click the ContextQA execution link in the Jira issue description to view full screenshots and video

Connect ContextQA to your CI/CD pipeline in 15 minutes. Book a Demo → — See the full integration walkthrough for your existing toolchain.

PreviousIntegrations Overview

NextAzure DevOps

Last updated 20 days ago

Was this helpful?