Move test cases and run history between Jira instances

Export every Zephyr Scale test case, plan, cycle and execution/run history into a portable archive you own — before an instance switch or an account closure locks it away.

• Current version: 1.0.0
• Works with: Jira Cloud + Zephyr Scale
• Pricing: £7.90 per month, flat, billed by Atlassian through the Marketplace
• Support: layercell.com/support
• Privacy notice: layercell.com/privacy

What it does

The app adds a Zephyr Scale Export page to your Jira instance. You point it at one Zephyr Scale source, it reads your test data through the Zephyr Scale REST API, and it writes a downloadable archive: one record per source test case, each with its test plan and test cycle assignments and its execution/run history. Download the finished archive as JSON or CSV.

The export is one-way and read-only. Nothing is written back to Jira or to Zephyr Scale, there is no import module, and there is no sync.

Install

1. Get the app from the Atlassian Marketplace.
2. Approve the permissions. The app requests exactly two scopes: read:jira-work (read the Jira side of your test data) and storage:app (its own storage). It requests no Jira write scope at all, and its backend talks only to your own site (*.atlassian.net) and to Zephyr Scale (api.zephyrscale.smartbear.com).
3. Open Apps → Zephyr Scale Export in the Jira top navigation.

Getting started

1. Configure the source. The page shows three fields:
   • Zephyr Scale base URL — leave the default (https://api.zephyrscale.smartbear.com/v2) unless support directs you otherwise.
   • Zephyr Scale API token — a token from your Zephyr Scale account. It is stored encrypted in the app's own storage and deleted when the app is uninstalled.
   • Jira project key — the project whose test data you are exporting.
2. Start the export. A progress view appears with per-entity counts — test cases, plans, cycles, executions — updating while the run proceeds, and a final status of completed, failed, or partial.
3. Download the archive when the job completes.

You can close the page mid-run. A background pump steps the export forward every few minutes whether or not anyone is watching, and an interrupted run resumes where it stopped — restarting never duplicates records.

Reading the results

• Archive contents: one JSON/CSV record per source test case with its plan and cycle assignments; executions and run history as the Zephyr Scale REST API reports them. If the API does not expose a field, it is absent from the archive rather than fabricated.
• Reconciliation report: for every test cycle the app compares the number of executions it wrote against the count the API reports for that cycle, and flags every cycle where the two differ — so a truncated export is visible, not silent.
• Partial status means the run finished with flagged cycles or skipped records; read the report before trusting the archive.

Access and tenant isolation

An archive is reachable only through its download link inside the Jira installation that created it. A request carrying another installation's context — or a bare direct URL — gets 403. There is no code path where a caller-supplied value selects another tenant's archive.

Archives are retained for 30 days after their export completes, then deleted by a daily retention sweep along with the job state behind them. Download what you need inside that window.

Data handling

• The only personal data the app stores is Jira account IDs recorded as authorship metadata on exported test data (who created, is assigned to, or executed a given item).
• Every person can export or erase everything the app holds about them through the app's built-in data-subject controls.
• Uninstalling purges your site's data, including the stored API token; the daily retention sweep catches anything left after that.
• No compensation, financial, or payment data is touched — the app handles test-management metadata only.

Limits and non-goals

• Export only: no import into a target instance, no remapping of users, issue links, statuses, or cycle history into another Jira.
• No bidirectional or ongoing sync: this is a one-time snapshot, not a live mirror.
• Zephyr Scale only — no Zephyr Squad and no other test tool.
• One configured source per installation; run one export job at a time.
• Archives expire 30 days after completion.

Pricing and billing

£7.90 per month flat, billed monthly by Atlassian through your Atlassian billing account. There is no per-user charge and no usage metering.

Layercell Ltd is a company registered in England and Wales, company number 17363808. Registered office: 111 Upper Grosvenor Road, Royal Tunbridge Wells, TN1 2EA.