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. You can use the API integration for server-side requirement sync and defect push, the Jira Plugin (Forge app) for full test management inside Jira, or the Chrome Extension for lightweight browser-based access. All three connect to the same TestKase project, so you can mix and match based on your team's needs.
API Integration
Server-side sync for requirements and defects between TestKase and Jira
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
Bidirectional sync
Requirements and defects stay in sync across platforms
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 | TestKase Settings | Install from Marketplace, configure in Jira | Install Chrome extension, login with PAT |
| Covers requirements | Yes (one-way sync) | Yes (automatic) | Yes (automatic) |
| Covers defects | Yes (push to Jira) | Yes (automatic) | Yes (automatic) |
| 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 support | Yes | No (Cloud only) | No (Cloud only) |
| 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 Jira issues synced as requirements or defects pushed back to Jira. This is the only option that supports Jira Server and Data Center.
- 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 page to manage test cases, execute tests, and push defects. Ideal for team members who work across multiple platforms and want a consistent experience.
If you are unsure, start with the API Integration for requirement sync and defect push. Add the Plugin or Extension later when your team wants to work directly from Jira or the browser.
Using Multiple Connection Types
The three connection types complement each other and can be used simultaneously on the same project:
- Set up the API Integration in TestKase Settings to keep requirements and defects in sync automatically.
- Install the Plugin so QA engineers working in Jira can create and execute test cases from the issue panel.
- Install the Chrome Extension for team members who prefer a lightweight browser-based workflow.
All changes made through any connection type are reflected in TestKase, so your test data stays consistent regardless of which integration your team uses.