Documentation

CaseRun is a Jira Cloud app built on Atlassian Forge. Everything below happens inside Jira — there is no separate account to create.

Install and open

Install CaseRun from the Atlassian Marketplace into your Jira site. Open any project and pick CaseRun in the project sidebar. The first load creates the app's tables and takes a few seconds; after that the list opens in well under a second.

The app asks for two read-only Jira scopes (read:jira-work, read:jira-user) so it knows which project you opened and who ran a test. It never creates, edits or deletes Jira issues.

Test cases

The Test cases tab holds your catalogue: folders on the left, tests on the right, 200 rows per page.

• New test creates a case; open it to edit the objective, precondition, labels, priority and the step table (action, test data, expected result).
• Search filters by title. Folder and search combine.
• Bulk actions: tick rows, or tick the header box and choose Select all N matching to select across pages. Then move to a folder, change priority, re-label, add to a cycle, or delete — each runs as one database statement, so thousands of tests finish in well under a second.

Cycles and runs

A cycle is one execution of a set of tests (a regression run, a release candidate, a smoke test).

1. Open Test cycles → New cycle and give it a name, environment and build.
2. Add tests — pick a folder/filter and add everything that matches in one action.
3. Press Record on a row to open the run drawer: mark each step Pass, Fail, Blocked or Skipped, and write what actually happened on the steps that failed.

The cycle header shows pass rate and progress as you go; the Reports tab shows pass rate over time, cycle progress, and the tests that fail most often with their last failure message.

Import from Excel, CSV, or another tool

Use Import CSV/Excel on the Test cases tab. You can paste cells straight from a spreadsheet (tab separated) or upload a .csv/.tsv file.

CaseRun recognises exports from Xray, Zephyr Scale, Zephyr Squad, TestRail and qTest and maps their column names for you. When a tool writes one row per step, the rows are grouped back into a single test case — by the case ID column when the file has one, otherwise by the convention that a blank title continues the previous case.

Column	Recognised names (examples)
Title	Title, Name, Summary, Test Summary, Test Case Name
Folder	Folder, Suite, Section, Module, Test Repo
Step	Step, Action, Test Step Description, Steps Separated (Step)
Expected result	Expected Result, Result, Test Script (Step-by-Step) - Expected Result
Test data	Data, Test Data

Tool-by-tool column tables (and what does not come across) are on the migration page.

Anything the mapping gets wrong you can change in the dropdowns before importing — the preview shows exactly how many cases and steps will be created.

Send CI results (JUnit XML)

Open the CI tab. CaseRun shows an ingest URL for your site and a ready-made snippet. Post the JUnit XML your test runner already produces:

curl -X POST "<your ingest URL>&cycle=Nightly&env=staging&version=$BUILD_NUMBER" \
     -H "Content-Type: application/xml" \
     --data-binary @junit-results.xml

Runner-by-runner configuration (Playwright, Cypress, pytest, Jest, Robot, Newman) and ready-made steps for GitHub Actions, GitLab CI, Jenkins and Bitbucket are on the CI setup page.

Playwright, Cypress, pytest, JUnit, TestNG, Jest, Mocha, Robot Framework and Newman all emit JUnit XML, and it works the same from GitHub Actions, Jenkins, GitLab CI, Bitbucket Pipelines or CircleCI.

• Tests in the file that don't exist yet are created automatically.
• Re-posting the same run does not duplicate results.
• Every ingest is logged with its time, cycle, counts and environment — so "nothing ran" is distinguishable from "nothing arrived".

Rotating the URL

The ingest URL works like a credential: anyone holding it can post results into your installation. Keep it in your CI secret store. If it leaks, press Rotate URL on the CI tab — the old address stops working immediately.

Requirement traceability

Link tests to Jira issues from the test detail view, or from the CaseRun panel on any issue. The issue panel lists the linked tests and their latest result, and you can link or unlink from there.

Data, limits and residency

All data lives in Forge hosted storage inside Atlassian's infrastructure, scoped to your installation. Nothing is sent to a CaseRun server, because there isn't one — which also makes the app eligible for Atlassian's data residency program.

Each installation has 1 GiB of storage. Execution history is stored in a compact encoding of about 98 bytes per run, which is roughly 10 million runs — for a team running 5,000 tests every week, decades of history.

Deleting tests, cycles or runs inside the app is immediate. When the app is uninstalled, Atlassian's data lifecycle applies: data is soft-deleted and kept for 28 days, then removed. See the privacy and data handling page for the full detail.

Getting help

Email support@caserun.dev. Include your Jira site URL and roughly when the problem happened — that is usually enough to find it.