_Last updated: 2026-09-02_
CaseRun runs entirely on Atlassian Forge. There is no CaseRun-operated server, and no CaseRun-operated
database. Everything the app stores lives in Forge hosted storage (Forge SQL) inside Atlassian's
infrastructure, scoped to your installation.
| Data | Why | Where |
|---|---|---|
| Test cases — title, objective, precondition, labels, folder, priority, status | The test catalogue you create | Forge SQL |
| Test steps — action, expected result, test data | Step-by-step instructions | Forge SQL |
| Test cycles and executions — status, timestamps, duration, environment, build | Run history | Forge SQL |
| Step results and failure comments | Why a run failed | Forge SQL |
| Links between tests and Jira issue keys | Requirement traceability | Forge SQL |
| CI ingest log — time, cycle, counts, environment, error text | So you can see whether a CI run arrived | Forge SQL |
| Atlassian account ID of the user who created or executed something | Attribution ("who ran this") | Forge SQL |
The app requests only two Jira scopes — read:jira-work and read:jira-user — and uses them to know
which project the page is opened in. CaseRun does not create, modify, or delete Jira issues.
The only personal identifier stored is the Atlassian account ID, an opaque identifier issued by
Atlassian. CaseRun does not store names, email addresses, avatars, or IP addresses.
Free-text fields (test titles, failure comments, notes, and anything your CI posts) are stored as you
enter or send them. Please avoid putting personal or sensitive data into those fields.
The CI ingest endpoint accepts a JUnit XML document that your pipeline posts. CaseRun parses it and
stores test names, statuses, durations, and failure messages (truncated to 2,000 characters).
The ingest URL functions as a credential — anyone holding it can post results into your installation.
Keep it in your CI secret store. You can rotate it at any time from the app's CI tab.
All in-scope data is stored exclusively in Forge hosted storage, which makes the app eligible for
Atlassian's data residency program: when a site admin pins their Jira site to a supported location,
eligible Forge apps are migrated and pinned along with it. See
CaseRun does not transfer data to any third party. There are no analytics SDKs, no external logging, and
no outbound calls to non-Atlassian services.
soft-deleted and retained for 28 days, after which it is removed. A reinstall is treated as a new
installation and does not restore previous data automatically; recovery must be requested within
21 days of uninstall. See
Data lifecycle for Forge-hosted storage.
When you contact support we only see what you choose to send us. There is no vendor-side console for
browsing your installation's data, and the app never exports data out of your Atlassian site.
Support: support@caserun.dev
Material changes to this document will be reflected in the app listing before they take effect.