Integrating PractiTest with Jira

PractiTest's Jira integration is bidirectional: defects logged in PractiTest appear in Jira, and Jira issues can be linked as requirements in PractiTest. This covers the full setup, the field mapping configuration that trips most teams up, and how to use the traceability matrix once everything is connected.

Prerequisites

You need:

• PractiTest account with a project set up
• Jira Cloud or Jira Server instance (PractiTest supports both)
• Jira admin access to create an API token and configure the integration
• PractiTest project manager role

Setting Up the Integration

In PractiTest, go to Settings > Integrations > Issue Trackers. Click Add New Integration and select Jira.

Fill in the connection details:

• URL: Your Jira base URL (e.g., https://yourcompany.atlassian.net for Cloud, or your server URL)
• Username: The Jira account email that will own the integration
• API Token: Generate this in Jira at Account Settings > Security > API tokens. For Jira Server, use a Personal Access Token instead.
• Project Key: The Jira project key (e.g., PROJ) where defects will be created

Click Test Connection before saving. If the connection fails, the most common cause is an API token scoped to the wrong account or a network firewall blocking outbound HTTPS from PractiTest to your Jira instance.

Linking Jira Issues as Requirements

Once the integration is active, go to Requirements in your PractiTest project. Click New Requirement and choose Import from Jira. You can filter by Jira JQL:

project = PROJ AND issuetype = Story AND status != Done

PractiTest pulls those issues and creates corresponding Requirement entities. From that point, any status change on the Jira issue is reflected in PractiTest's requirement view automatically.

To link an existing Requirement to a Jira issue manually: open the Requirement, click Link Issue, and paste the Jira issue key (e.g., PROJ-456).

Linking Test Cases to Requirements

With requirements imported, you can link test cases to them. In the Test Library, open a test case and go to the Requirements tab. Click Add Requirement and select the relevant Jira-backed requirement. One test case can cover multiple requirements. One requirement can have many test cases.

This link is what powers the traceability matrix -- the report that shows which requirements have test coverage and what the current pass/fail state is.

Syncing Defects from PractiTest to Jira

When a tester marks a test step as Failed during a Test Run, they can click Add Defect. This opens a dialog with fields mapped to Jira issue fields. Fill in the description and severity, and PractiTest creates a Jira issue automatically.

The created Jira issue is linked back to the test instance. If the Jira issue is later resolved, PractiTest shows its status next to the test instance without any manual update.

Field Mapping Configuration

This is where most teams spend the most time. In the integration settings, click Field Mapping to configure which PractiTest fields map to which Jira fields.

Default mappings:

• PractiTest Defect Name -> Jira Summary
• PractiTest Defect Description -> Jira Description
• PractiTest Severity -> Jira Priority

Custom field mapping is more involved. If your Jira project has a required field (e.g., a "Team" dropdown that's mandatory on issue creation), you need to either map a PractiTest custom field to it or set a static default value. To set a static default: in the Field Mapping panel, find the Jira field, and choose Fixed Value instead of a PractiTest field.

A common misconfiguration: PractiTest sends Priority = High but your Jira project uses a custom priority scheme where High is not a valid value. The defect creation silently fails. Check the PractiTest integration logs under Settings > Integrations > Logs to see the exact API error returned by Jira.

Requirement Traceability Matrix

Once requirements are linked to test cases and test cases have been executed, go to Reports > Traceability Matrix. The matrix shows:

• Each requirement (row)
• Linked test cases (columns)
• Execution status per test instance: Pass, Fail, No Run, Blocked

You can filter by release or test set to scope it to a specific iteration. Export to PDF or Excel using the export button in the top right.

This matrix is the artifact most useful for release sign-off conversations. It makes "which requirements have test coverage" and "which requirements have failures" answerable in one view.

Bidirectional Status Sync

By default, status changes only flow one direction: Jira changes update PractiTest requirements, but PractiTest test results do not update Jira issue status. If you want PractiTest to close a Jira story when all linked tests pass, configure the Status Mapping under integration settings. Map All Tests Passed to Jira Transition: Done (or whatever your workflow calls it).

Use this carefully -- automatic Jira transitions based on test results can close issues prematurely if not all test sets have been executed.

Next Step

Connect the integration, import 10 Jira stories as requirements, link them to your existing test cases, and run one test set. Then open the Traceability Matrix -- that first look at real coverage data is where the value of the integration becomes concrete.