Jira Integration

Overview

The Jira integration connects TestKase with your Jira instance to create a seamless bridge between test management and issue tracking. When connected, Jira issues are automatically imported as requirements, changes in Jira are reflected in TestKase in real time, and linked test cases appear as comments on the Jira issue -- eliminating manual data entry and keeping both systems in sync.

This integration is especially valuable for teams that manage their product backlog in Jira and want to maintain full traceability from requirements through test cases to defects.

Prerequisites

Before setting up the Jira integration, make sure you have the following ready:

For Jira Cloud

1. An active Jira Cloud account with a project containing issues.
2. An API token generated from your Atlassian account.
3. Your Jira email address (used alongside the API token for authentication).
4. The instance URL of your Jira site (e.g., https://your-org.atlassian.net).

For Jira Server / Data Center

1. Your Jira Server or Data Center base URL (e.g., https://jira.yourcompany.com).
2. A Personal Access Token (PAT) from your Jira profile settings.
3. The PAT must have read and write permissions on the target project.

TestKase Permissions

You must have Project Admin or Owner role in the TestKase project to configure integrations. See User Permissions for details.

Setup

Follow these steps to connect your TestKase project to a Jira Cloud or Jira Server instance:

1. Navigate to Settings → Jira Integration in your TestKase project.
2. You will see the integration setup card. Click Configure.
3. Select Jira as your platform.
4. Enter your Instance URL:
   • Jira Cloud: https://your-org.atlassian.net
   • Jira Server: https://jira.yourcompany.com
5. Enter your Email address (Jira Cloud only -- this is the email associated with the API token).
6. Paste your API Token (Jira Cloud) or Personal Access Token (Jira Server).
7. Click Connect. TestKase validates the credentials and fetches your Jira projects.
8. Select the Jira project you want to link to this TestKase project.
9. Select the Issue Type to use when creating issues from TestKase defects (e.g., Bug, Task, Story).
10. Click Save to complete the connection.

Auto-Sync

Once connected, TestKase automatically syncs Jira issues as requirements in real time. There is no manual import step required -- the integration keeps both systems in sync continuously.

How Auto-Sync Works

• Automatic import -- Jira issues from the connected project are automatically imported as requirements in TestKase. The Jira issue summary becomes the requirement title, and the Jira description becomes the requirement description. The Jira issue key (e.g., PROJ-123) is stored as a clickable reference.
• Real-time updates -- When a Jira issue is updated (title changes, description edits, status transitions, priority changes), those changes are reflected in TestKase automatically.
• Test case comments -- When test cases are linked to a synced requirement in TestKase, the linked test cases appear as comments on the corresponding Jira issue. This gives your Jira users visibility into test coverage without leaving Jira.
• Bidirectional defect sync -- Defect updates sync bidirectionally between TestKase and Jira. Status changes, priority updates, and comments are reflected in both systems.

Synced Requirement Behavior

• Synced requirements display a Jira badge showing the original Jira issue key. Clicking the badge opens the Jira issue in a new tab.
• The title and description of synced requirements are read-only in TestKase because the source of truth is Jira. To edit them, make changes in Jira and they will sync over.
• You can still link test cases and defects to synced requirements, add attachments, and assign them to folders within TestKase -- these fields are managed locally.
• If a Jira issue is deleted, the synced requirement in TestKase is automatically marked as Deprecated rather than deleted, preserving any test case links and historical data.

Field Mapping

TestKase automatically maps fields between Jira and TestKase. The following fields are mapped during sync:

Priority Mapping

Traceability from Test Cases

From the test case detail view, you can link test cases to Jira-synced requirements. This creates a traceable connection between your Jira backlog and your test suite.

When a test case is linked to a synced requirement, TestKase automatically posts a comment on the corresponding Jira issue showing the linked test case details. This gives Jira users direct visibility into which tests cover each issue -- without leaving Jira.

Defect Push

Push defects from TestKase to Jira, creating new issues automatically with all relevant information.

How Defect Push Works

1. Open a defect in TestKase.
2. Click the Push to Jira button.
3. TestKase creates a new issue in your connected Jira project with the defect details.
4. A bidirectional link is established -- the TestKase defect shows a link to the Jira issue, and the Jira issue description includes a reference back to TestKase.

Field Mapping for Defects

Creating Defects During Execution

The most common workflow is to create defects directly during test execution. When a test case fails and you create a defect from the execution screen, the defect is automatically linked to the test case and the test cycle. If the Jira integration is connected, you can immediately push the new defect to Jira with one click.

Management

Edit Connection

To update your integration settings (project, issue type, or credentials):

1. Navigate to Settings → Jira Integration.
2. Click Edit on the integration card.
3. Modify the fields you want to update (e.g., change the issue type, update the access token).
4. Click Save to apply changes.

Disconnect (Reset)

To completely remove the integration:

1. Click Reset on the integration card.
2. Confirm the disconnection.

What happens when you disconnect:

• Auto-sync stops between TestKase and Jira.
• Existing imported requirements are preserved in TestKase -- they are not deleted.
• Existing pushed defects remain in Jira -- they are not removed.
• Cross-reference links on existing items continue to work (they link to the Jira URL).
• Previously synced requirements become editable in TestKase.
• You can reconnect to the same or a different project at any time.

Troubleshooting

▶I see an 'Authentication failed' error

This usually means your access token is invalid or expired. Steps to resolve:

1. Verify the token is still valid in your Jira account settings.
2. For Jira Cloud, ensure you are using the correct email address (the one associated with the API token).
3. For Jira Server, confirm the PAT has not been revoked by an administrator.
4. Generate a new token and update the integration in TestKase.

▶I can't see my Jira project in the dropdown

Your access token may not have access to that project. Common causes:

• The token user does not have permission to access that Jira project.
• The project is archived or deleted in Jira.
• For Jira Cloud, the token scope may be limited. Create a new token with full project access.

▶Synced requirements are missing description or priority

TestKase maps the most common fields (title, description, priority, status). If a field is empty in the source issue, it will be empty in TestKase. Custom Jira fields (like Story Points, Sprint, or custom dropdowns) are not synced automatically -- you can add these details manually or use custom fields.

▶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.

▶The integration was working but suddenly stopped

Most common causes:

• Token expired: Generate a new token and edit the integration.
• Jira project was moved or renamed: Edit the integration and re-select the project.
• Network/firewall change: Ensure TestKase can reach your Jira Server instance.

▶Can I connect multiple Jira projects to one TestKase project?

No. Each TestKase project supports one external integration connection at a time. To work with multiple Jira projects, create separate TestKase projects for each. This keeps the traceability clean and avoids cross-project confusion.

▶What happens to synced requirements if I disconnect?

Synced requirements remain in TestKase as regular requirements. They are no longer read-only and can be edited directly. The Jira badge is removed, and the requirements become fully managed within TestKase. No data is lost during disconnection.

▶Can I use the same Jira token for multiple TestKase projects?

Yes. The same Jira API token can be used across multiple TestKase projects. Each project connects to a different Jira project using the same token, as long as the token user has access to all the Jira projects.

▶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.

▶Is Jira Service Management supported?

Jira Service Management projects are supported as long as the issue type you select (e.g., Bug, Task) is available in the project. Service request-specific fields may not be mapped.