Jira Integration
Push defects to Jira, sync status bidirectionally, and maintain traceability between TestKase and Jira.
Overview
The Jira integration for defects allows you to push defects from TestKase directly to Jira as new issues and keep them in sync bidirectionally. When a defect is created in TestKase, it can be exported to Jira with one click. Status updates, priority changes, and comments are reflected in both systems automatically, ensuring your development and QA teams stay aligned without manual data entry.
One-click push
Push defects to Jira as new issues instantly
Bidirectional sync
Status and priority changes reflected in both systems
Cross-reference links
Click-through links between TestKase defects and Jira issues
Field mapping
Priority and status mapped automatically
Secure
Tokens stored encrypted, never exposed
Non-destructive
Disconnect anytime, pushed defects remain in Jira
Prerequisites
Before pushing defects to Jira, you must have the Jira integration connected to your TestKase project. If you have not set it up yet, follow the Jira Integration setup guide.
You will need:
- An active Jira integration connection in your TestKase project settings.
- The integration configured with an issue type for defects (e.g., Bug, Task).
- Project Admin or Owner role in TestKase, or the appropriate permissions to create defects and use integrations.
Push a Defect to Jira
When you discover a defect and want to create a corresponding Jira issue:
- Open the defect in TestKase from the defects list.
- Click the Push to Jira button in the defect detail view.
- TestKase creates a new issue in your connected Jira project with the defect details.
- A bidirectional link is established -- the TestKase defect shows a clickable link to the Jira issue, and the Jira issue description includes a reference back to TestKase.
The issue type used when creating Jira issues is configured during the integration setup. Most teams choose Bug for defect tracking. You can change this at any time by editing the integration settings.
Push During Test Execution
The most common workflow is to push defects during test execution:
- Execute a test case in a test cycle.
- When a test fails, create a defect directly from the execution view.
- The defect is automatically linked to the failed test case.
- Click Push to Jira to immediately create the Jira issue.
This captures the most context (test case, cycle, execution details) and ensures no information is lost between discovery and reporting.
Bidirectional Sync
Once a defect is pushed to Jira, changes are synchronized between both systems automatically:
- Status updates -- When the Jira issue status changes (e.g., from To Do to In Progress to Done), the corresponding defect status in TestKase updates automatically. Similarly, status changes in TestKase are reflected in Jira.
- Priority changes -- Priority updates in either system are synced to the other.
- Comments -- Comments added on the Jira issue appear on the TestKase defect, and vice versa.
The sync is automatic and continuous. You do not need to manually trigger updates after the initial push.
Field Mapping
TestKase automatically maps defect fields to Jira issue fields when pushing:
| TestKase Defect Field | Jira Issue Field | Notes |
|---|---|---|
| Title | Summary | Mapped directly |
| Description | Description | Includes a link back to the TestKase defect |
| Priority | Priority | Mapped to closest Jira level (see table below) |
| Status | Status | Mapped based on status workflow |
Priority Mapping
| TestKase Defect Priority | Jira Priority |
|---|---|
| Blocker | Highest / Blocker |
| Critical | High / Critical |
| Major | Medium |
| Minor | Low |
| Trivial | Lowest |
Status Mapping
| TestKase Status | Jira Status |
|---|---|
| Open | To Do / Open |
| In-Progress | In Progress |
| Closed | Done / Closed |
| Achieved | Done / Closed |
Priority mapping is automatic. If your Jira instance uses custom priority schemes, the mapping uses the default Jira priority levels. You can manually adjust priority values after push if needed.
Viewing Pushed Defects
After a defect is pushed to Jira, the defect detail view in TestKase displays:
- A Jira badge with the issue key (e.g., PROJ-456). Clicking the badge opens the Jira issue in a new tab.
- The current sync status showing when the last sync occurred.
- Any comments from the Jira issue.
From the Jira side, the created issue includes:
- The defect title as the issue summary.
- The defect description with a link back to TestKase.
- The mapped priority and status.
Management
What Happens on Disconnect
If you disconnect the Jira integration:
- Previously pushed defects remain in Jira -- they are not deleted.
- The cross-reference links on existing defects continue to work (they link to the Jira URL).
- No further sync operations occur until you reconnect.
- You can reconnect at any time to resume syncing.
Troubleshooting
▶Pushed defect is not appearing in Jira
Check the following:
- The issue type selected in the integration settings exists and is enabled for the Jira project.
- The token user has permission to create issues in the Jira project.
- Required fields in Jira (besides summary and description) may be blocking issue creation. Simplify your Jira issue type's required fields.
▶Status changes are not syncing
Verify that:
- The Jira integration is still connected (check Settings → Jira Integration).
- Your access token has not expired. Generate a new token and update the integration if needed.
- The Jira workflow allows the status transition. Some Jira projects have restricted workflows that prevent certain transitions.
▶Can I push a defect to a different Jira project?
Each TestKase project is connected to one Jira project. All pushed defects go to that project. To push defects to a different Jira project, edit the integration settings and change the connected project, or create a separate TestKase project for each Jira project.
▶Does disconnecting delete pushed defects from Jira?
No. Disconnecting only removes the integration link in TestKase. Issues created in Jira via defect push are permanent and remain in Jira regardless of the TestKase integration status.