Jira
Three ways to connect TestKase with Jira -- API integration, native Jira Plugin (Forge app), and Chrome Extension.
Overview
TestKase offers three distinct connection types for Jira, each designed for different workflows and team preferences. Use the API integration to search Jira issues from TestKase and link them to test cases, the Jira Plugin (Forge app) for test management inside Jira, or the Chrome Extension for lightweight browser-based access. A TestKase project uses one of them at a time, so pick the one that matches how your team works. All three require Jira Cloud.
API Integration
Search Jira issues from TestKase and link them to test cases as requirements
Plugin (Forge App)
Native Jira panel for test case management, execution, and AI generation
Chrome Extension
Browser side panel for quick test management from any Jira page
On-demand refresh
Pull the latest Jira issue status into TestKase when you refresh -- there is no background sync
AI test generation
Generate test cases from Jira context via the Plugin or Extension
Test execution
Run tests inside Jira or from the browser side panel
Connection Types at a Glance
| Feature | API Integration | Plugin (Forge App) | Chrome Extension |
|---|---|---|---|
| Where configured | Jira card under API Integrations on the Requirement Integration page | Jira Plugin card under Plugin Integrations, plus install from the Marketplace | Jira card under Chrome Extension, plus install the extension and log in with a PAT |
| Covers requirements | Yes (one-way sync) | Yes (automatic) | Yes (automatic) |
| Covers defects | Push to Jira not yet available -- link existing issues only | Configuration covers both types; no defect UI in the panel | Configuration covers both types; no defect UI in the panel |
| Scope per setup | Requirements OR defects separately | Both together | Both together |
| Test case management | In TestKase only | Inside Jira | Browser side panel |
| AI test generation | In TestKase only | Inside Jira | From side panel |
| Test execution | In TestKase only | Inside Jira | From side panel |
| Jira Server / Data Center support | No | No | No |
| Best for | Teams managing tests in TestKase | QA teams working in Jira | Quick access from any platform |
Which Should I Use?
- API Integration -- Best when your team primarily works inside TestKase and needs to search Jira issues and link them to test cases. Requires Jira Cloud.
- Plugin (Forge App) -- Best when your QA team lives in Jira and wants to create test cases, run executions, and generate AI test cases without switching to another tool. Requires Jira Cloud.
- Chrome Extension -- Best for quick, lightweight access. Open a side panel from any Jira issue page to manage test cases, generate them with AI, and execute tests. Ideal for team members who work across multiple platforms and want a consistent experience. Requires Jira Cloud.
If you are unsure, start with the API Integration for searching and linking Jira issues. You can change to the Plugin or Extension later, but it replaces the API configuration rather than adding to it -- see below.
Choosing One Connection Type
A TestKase project uses one connection type at a time. Selecting API Integration, Plugin, Chrome Extension or Built-in on the Requirement Integration page replaces whatever was configured before -- TestKase warns you before it does.
The API Integration is configured separately for requirements and for defects. The Plugin and the Chrome Extension always cover both types with a single configuration, so connecting either one also replaces the other type's setup.
Each surface only recognises projects connected through its own card. A Jira project connected through the Jira card under API Integrations is invisible to the Plugin and to the Extension, and vice versa.
Switching is destructive when the option you replace is Built-in. Connecting any of the three -- the API Integration, the Jira Plugin or the Chrome Extension -- to a project whose requirement integration is Built-in permanently deletes that project's requirements and requirement folders; on the Defect Integration page it deletes the project's built-in defects. The Plugin and the Extension cover both types at once, so they delete the other type's built-in data too. Nothing is migrated to Jira and nothing can be recovered. See Built-in before you switch.