Troubleshooting

This means no PAT has been saved for your user. Navigate to the TestKase global page in Jira (find it in the apps menu), enter your PAT, and click Save. The configuration is per-user, so each team member must set up their own PAT.

Try these steps:

1. Refresh the Jira issue page.
2. Verify your PAT is valid by testing it in the TestKase API or checking Settings → API Keys.
3. Ensure the Jira project is connected to a TestKase project via Jira Integration in TestKase Settings.
4. Check your browser console for network errors -- the Forge app may be unable to reach the TestKase API.

Possible causes:

• No test cases linked: The panel shows test cases linked to the current Jira issue. If no test cases have been linked or created from this issue, the table will be empty.
• Wrong project: Verify that the Jira project is mapped to the correct TestKase project. Test cases from a different project will not appear.
• Pagination: If you have many test cases, check subsequent pages using the pagination controls.

The Generate Testcase button is disabled when AI features are turned off for your organization. Ask your organization owner to enable AI features from TestKase Settings. The button tooltip will read "AI features are temporarily unavailable. Contact your admin."

Ensure you have:

1. Selected a status (Not Executed, Pass, Fail, or Blocked) -- the Save button is disabled until a status is chosen.
2. A stable network connection -- the Forge app needs to reach the TestKase API to save execution data.
3. A valid PAT -- if your token has expired, saves will fail silently. Refresh your PAT if needed.

Check the following:

• File format: Only PDF, PNG, JPG, GIF, WEBP, MP4, AVI, MOV, XLSX, XLS, CSV, DOC, and DOCX files are supported.
• File size: Large files may exceed upload limits. Try compressing the file or reducing resolution for images/videos.
• Storage quota: Your TestKase organization may have reached its storage limit. Check Settings → Storage in TestKase.

Folders are loaded based on the TestKase project mapped to the current Jira project. If you do not see expected folders:

• Verify the project mapping is correct (check TestKase Settings → Jira Integration).
• Ensure you have permission to view folders in the mapped TestKase project.
• Try expanding parent folders -- child folders are hidden until the parent is expanded.

The plugin makes API calls to TestKase on each load. Slow loading can be caused by:

• Network latency between your Jira Cloud instance and the TestKase API.
• Large datasets -- projects with thousands of test cases may take longer to load. Use search and pagination to narrow results.
• Forge cold starts -- the first load after a period of inactivity may be slower due to Forge infrastructure warm-up. Subsequent loads are faster.

Yes. Each user configures their own PAT, and all actions are independent. Multiple team members can create test cases, execute tests, and manage cycles on the same or different Jira issues simultaneously. Each user's actions are attributed to their TestKase account.

Navigate to the TestKase global page in Jira (accessible from the apps menu). Enter your new PAT and click Save. The old token is replaced immediately. You can generate a new PAT from TestKase Settings → API Keys.

The plugin stores only the user's PAT in Forge's encrypted storage (per-user, per-instance). All test management data (test cases, cycles, executions, folders) is stored in TestKase, not in Jira. The plugin reads Jira issue context (title, description, project key) but does not write to or modify Jira issues.