Test Case Management

Create, view, link, unlink, and manage test cases directly from the Jira issue panel.

Overview

The Test Cases tab in the Jira plugin panel provides full test case management for the current Jira issue. You can view linked test cases, create new ones, link existing ones from your TestKase project, and perform bulk operations -- all without leaving Jira.

Header Action Buttons

Three action buttons are always visible at the top of the Test Cases tab:

Generate Testcase (Sparkles icon) -- Opens the AI test generation modal to create test cases from the Jira issue context. If AI features are disabled for your organization, the button is grayed out with a tooltip: "AI features are temporarily unavailable. Contact your admin." See AI Test Generation for details.
Create Testcases (Plus icon) -- Opens the advanced create modal where you can fill in all test case fields manually.
Link Testcases with Issue (Link icon) -- Opens the link modal to browse and select existing test cases from your TestKase project.

Test Case Table

The main area displays a table of test cases linked to the current Jira issue.

Columns

All columns are sortable by clicking the column header:

Column	Description
ID	TestKase test case identifier
Title	Test case title (clickable -- opens the View Testcase modal)
Priority	Test case priority. Out of the box the values are Blocker, Critical, Major, Minor, Trivial; a project admin can change the list in TestKase
Last Execution Status	Status from the most recent test run
Last Execution Cycle	Name of the cycle where the test was last executed
Last Run Date	Date of the most recent execution

Search

A search bar above the table lets you filter test cases. Search requires a minimum of 3 characters and is debounced at 400ms to avoid excessive API calls.

Pagination

The table includes full pagination controls: First, Previous, Page numbers, Next, and Last.

Each test case row has a three-dot menu (⋮) with three actions:

Add to Test Cycle (Plus icon) -- Opens the AddToCycleModal where you can select a test cycle and link this test case to it. See Test Cycle Management for details.
UnLink Testcase (Link icon) -- Removes the link between this test case and the current Jira issue. The test case itself remains in TestKase -- only the issue mapping is removed.
Delete Testcase (Trash icon) -- Permanently deletes the test case from TestKase. This action cannot be undone.

Deleting a test case removes it permanently from TestKase, including all execution history. Use UnLink instead if you only want to disassociate it from the current Jira issue.

Linking Existing Test Cases

Click the Link Testcases with Issue button to open the LinkTestcasesModal. This modal uses a three-panel layout:

Left Panel -- Folder Tree

Displays the test case folder hierarchy with expand/collapse controls
Search box to filter folders by name
Three-dot menu (⋮) on each folder with:
- Edit Folder -- Rename the folder inline
- Delete Folder -- Remove the folder
Root-level hover actions:
- Create Folder (FolderPlus icon) -- Create a new folder at the root level
- Create Testcase (FilePlus2 icon) -- Quick-create a test case at root level

Middle Panel -- Test Case List

Tabs: All Test Cases | Unmapped | Archive
Checkboxes on each test case for selection
Select All / Deselect All toggle in the header
Search box to filter test cases
Click a test case to preview it in the right panel

Right Panel -- Preview

Displays the selected test case details including title, summary, precondition, test steps, and attachments
Read-only preview for reviewing before linking

Bottom Actions

Cancel -- Close the modal without linking
Link Selected -- Links the selected test cases to the current Jira issue. Shows the count of selected items.

Creating Test Cases

Click the Create Testcases button to open the CreateTestcaseModal.

Folder Selection

At the top of the form, a folder selection button opens the FolderSelectionModal where you can choose the destination folder for the new test case.

Form Fields

Field	Required	Description
Title	Yes	The test case title
Summary	No	Brief description of what the test covers
Precondition	No	Rich text editor for prerequisites (supports formatting)
Test Steps	No	Repeatable step entries, each with Description, Test Data, and Expected Result
Priority	No	Dropdown. Default values Blocker, Critical, Major, Minor, Trivial -- the list comes from your project's field configuration
Owner	No	Searchable dropdown of team members
Attachments	No	Drag-and-drop or click-to-browse file upload

Other system fields your project has switched on -- Status, Automated, Labels, Features, Platform, Environment, Test Data, Expected Result -- also appear here, and any field a project admin has marked mandatory is required in the plugin too.

Project custom fields are not shown in the plugin. The Create and View forms hide the custom_fields group, along with the requirement- and defect-link fields. Fill those in from the TestKase web app.

Test Steps

Each test step has three fields:

Description -- What action to perform
Test Data -- Input data for the step
Expected Result -- What should happen

You can add, delete, and drag-reorder steps.

Attachments

Supported file formats: PDF, PNG, JPG, GIF, WEBP, MP4, AVI, MOV, XLSX, XLS, CSV, DOC, DOCX.

Each uploaded attachment shows:

View (Eye icon) -- Preview the attachment
Delete (Trash icon) -- Remove the attachment

Submit

Click Create to save the test case. It is automatically linked to the current Jira issue.

Viewing and Editing a Test Case

Click a test case title in the table to open it.

The header shows the test case title, its ID, and an Open in TestKase icon that opens the full record in the TestKase web app in a new tab.
The body is a single editable form -- there are no Details/Edit tabs and no three-dot menu inside the modal. Row-level actions such as Add to Test Cycle, UnLink Testcase and Delete Testcase live on the test case row in the table.
Requirement- and defect-link fields are not shown in the plugin. Manage those in the TestKase web app.

Which fields appear depends on your project's field configuration. If you do not see a field you expect, check your project's field settings in TestKase.