Jira Link vs Jira Sync
Understand the differences between TestKase's API-based Jira Integration and the Forge-based Jira Plugin.
Overview
TestKase offers two complementary ways to work with Jira:
- Jira Link -- The API-based integration configured in TestKase Settings. It syncs requirements, pushes defects, and posts auto-comments on Jira issues.
- Jira Sync (Plugin) -- The Forge-based app installed in Jira. It adds a native panel to Jira issues for full test management from within Jira.
Both can be used independently or together. This page explains the differences and when to use each.
Comparison
| Feature | Jira Link | Jira Sync (Plugin) |
|---|---|---|
| Where configured | TestKase Settings → Jira Integration | Atlassian Marketplace → installed in Jira |
| Authentication | Shared Jira API token | Per-user TestKase PAT |
| UI location | TestKase web application | Native Jira issue panel |
| Issue type filtering | Manual selection during setup | All issue types auto-available |
| Auto-comments on Jira | Yes -- test case links posted as comments | No |
| Requirement sync | Yes -- Jira issues imported as requirements | No -- reads existing TestKase data |
| Defect push | Yes -- push defects from TestKase to Jira | No |
| Test case creation | From TestKase only | From Jira panel |
| Test execution | From TestKase only | From Jira panel |
| AI test generation | From TestKase only | From Jira panel |
| Test cycle management | From TestKase only | From Jira panel |
| Folder management | From TestKase only | From Jira panel |
| Best for | Teams working primarily in TestKase | Teams working primarily in Jira |
Jira Link (API Integration)
The Jira Link integration is configured in TestKase under Settings → Jira Integration. It uses a shared Jira API token to:
- Import Jira issues as requirements in TestKase with automatic sync
- Push defects from TestKase to Jira as new issues
- Post auto-comments on Jira issues when test cases are linked
- Sync field updates (status, priority) bidirectionally
This integration is ideal for teams that do most of their test management work in TestKase but need traceability back to Jira.
For setup instructions, see Jira Integration.
Jira Sync (Forge Plugin)
The Jira Sync plugin is installed from the Atlassian Marketplace and adds a native panel to every Jira issue. It uses per-user TestKase PATs to:
- Create and manage test cases directly from Jira issues
- Execute tests and record results from the Jira panel
- Generate test cases with AI using the Jira issue context
- Manage test cycles including creating, linking, and executing
- Organize with folders using the same hierarchy as TestKase
This integration is ideal for teams that spend most of their time in Jira and want full test management capabilities without switching to TestKase.
For setup instructions, see Installation and Setup & Authentication.
Using Both Together
The two integrations work best together:
- Jira Link handles requirement sync and defect push -- keeping your Jira backlog and TestKase requirements aligned, and ensuring defects appear in Jira for developer triage.
- Jira Sync (Plugin) handles day-to-day testing -- letting QA testers create test cases, execute tests, and manage cycles directly from the issues they are testing.
This gives you full bidirectional coverage: requirements flow from Jira to TestKase via Jira Link, and test management happens in Jira via the Plugin.
Setup Relationship
The Jira Plugin requires the Jira Link integration to be configured first. The plugin relies on the project mapping established by the Jira Link integration (in TestKase Settings → Jira Integration) to know which TestKase project corresponds to each Jira project.
Setup order:
- Configure Jira Link in TestKase Settings → Jira Integration (connects the Jira project to a TestKase project)
- Install the Jira Plugin from the Atlassian Marketplace
- Each user enters their PAT in the plugin's global page