TestKase Docs
Core TestingRequirements

TestKase Jira Plugin

Two-way test case management from within Jira using the TestKase plugin.

Overview

TestKase provides a Jira plugin that brings complete test management capabilities directly into your Jira interface. With the plugin installed, your team can create test cases, link test cycles, view execution status, and manage requirements -- all from within Jira. Two-way communication means there is no need to switch to the TestKase portal for day-to-day test management tasks.

Create test cases

Create test cases directly from any Jira issue

Link test cycles

Link Jira issues to TestKase test cycles and track progress

View execution status

See pass/fail counts and coverage directly on Jira issues

Two-way sync

Changes in Jira reflect in TestKase and vice versa

Manage requirements

View requirement traceability data from within Jira

Seamless integration

Plugin connects via TestKase API with PAT authentication

What the Plugin Does

The TestKase Jira Plugin adds a dedicated panel to your Jira issues that provides full test management capabilities without leaving Jira:

  • Create test cases from any Jira issue -- they appear in TestKase automatically.
  • Link test cycles to Jira issues and view cycle progress from Jira.
  • View execution status including pass/fail counts and coverage metrics.
  • Manage requirements linked to the Jira issue with full traceability data.
  • Bidirectional sync -- all changes flow between Jira and TestKase in real time.

Installation

From Atlassian Marketplace

  1. Go to the Atlassian Marketplace and search for "TestKase".
  2. Click Install (or Try it free for the trial period).
  3. Select the Jira instance where you want to install the plugin.
  4. Follow the prompts to complete installation. You will need Jira Admin permissions.

Manual Installation (Jira Server / Data Center)

  1. Download the plugin JAR file from the TestKase portal.
  2. In Jira, navigate to AdministrationManage AppsUpload App.
  3. Upload the JAR file and wait for installation to complete.
  4. The plugin will appear in the list of installed apps.

After installation, the TestKase panel will appear on all Jira issues. Individual users can collapse the panel if they do not need it for a particular issue.

Getting Started

After installation, the TestKase plugin panel appears on every Jira issue in the right sidebar or below the issue details (depending on your Jira layout).

  1. Open any Jira issue.
  2. Locate the TestKase panel.
  3. Click Connect to link the plugin to your TestKase account.
  4. Enter your TestKase Personal Access Token (PAT). See API Keys for how to generate a PAT.
  5. Select the TestKase project to connect to.
  6. The panel is now active and shows test case and requirement data for this issue.

Create Test Cases from Jira

Create test cases directly from a Jira issue without leaving the Jira interface:

  1. Open the Jira issue you want to create a test case for.
  2. In the TestKase panel, click Create Test Case.
  3. Fill in the test case details: title, steps, expected results, and priority.
  4. Click Save. The test case is created in TestKase and linked to the Jira issue.

The new test case appears in both the Jira issue's TestKase panel and in the TestKase project's test case list. Any changes made to the test case in either system are reflected in both.

Link Jira issues to TestKase test cycles to track testing progress from within Jira:

  1. In the TestKase panel on a Jira issue, click Link Test Cycle.
  2. Browse or search for available test cycles in the connected TestKase project.
  3. Select the test cycle and click Link.

Once linked, the panel shows the cycle's progress bar, pass/fail counts, and completion percentage. As testers execute tests in TestKase, the Jira panel updates in real time.

View Execution Status

The TestKase panel displays real-time test execution data for each linked test cycle:

  • Progress bar -- Color-coded bar showing pass (green), fail (red), blocked (yellow), skipped (blue), and not executed (gray) distribution.
  • Pass/fail counts -- Numeric counts for each execution status.
  • Coverage percentage -- Overall test coverage for requirements linked to this issue.

This gives product managers and developers immediate visibility into testing progress without opening TestKase.

Manage Requirements

When a Jira issue is synced as a requirement in TestKase (via the Jira Integration), the plugin panel shows the requirement's traceability data:

  • Linked test cases -- Which test cases verify this requirement.
  • Linked defects -- Which defects impact this requirement.
  • Coverage status -- Whether the requirement is covered, uncovered, or at risk.

Two-Way Sync

The TestKase Jira Plugin maintains bidirectional synchronization:

  • Jira → TestKase -- Changes to the Jira issue (title, description, status, priority) are reflected in the synced requirement in TestKase.
  • TestKase → Jira -- Test case links, execution results, and defect updates made in TestKase are reflected in the Jira issue's TestKase panel.
  • Comments -- Test execution comments and linked test case details appear as comments on the Jira issue.
  • Status updates -- When a synced requirement's linked test cases are executed, the results are visible in real time on the Jira issue.

How It Works

The TestKase Jira Plugin connects to the TestKase platform via the TestKase REST API:

  • Authentication -- The plugin uses a Personal Access Token (PAT) to authenticate with TestKase. Each user configures their own PAT for personalized access.
  • Data flow -- The plugin makes API calls to fetch test case, cycle, and requirement data from TestKase and displays it within the Jira interface.
  • Real-time updates -- The plugin polls for changes at regular intervals to keep the displayed data current.
  • Security -- PATs are stored securely within Jira's credential store. All communication between the plugin and TestKase uses HTTPS encryption.

For the best experience, ensure that your TestKase PAT has access to the projects you want to manage from Jira. Use a dedicated service account PAT for shared team access. See API Keys for token management best practices.