How to manage test cases in Jira Cloud without a plugin

Jira Cloud has no built-in test management, but you can get surprisingly far with features you already pay for. Here is a clean no-app setup, the limits teams usually hit, and how to tell when an app is worth it.

Step 1: give tests their own home

Create a separate project (for example QA) or a dedicated board for tests, so test cases do not clutter delivery boards, sprint reports or velocity.
Ask a Jira admin to add a work type (issue type) called Test in Settings > Work items > Work types and add it to that project.
Use components or labels for areas such as checkout or login, and keep a regression label for the cases you rerun every release.

Step 2: decide where steps live

Description template: a numbered list with Preconditions, Steps, Test data and Expected result headings. Simple and searchable.
Custom fields: paragraph fields for Preconditions and Expected result, plus a select field for priority or test type (manual, automated).
Bulk create from a spreadsheet: if your cases live in Google Sheets or Excel, the built-in CSV import can create one Test per row. See migrating test cases from CSV for column tips.

Step 3: a workflow for results

Give the Test work type a small workflow such as Not run, Passed, Failed and Blocked. When a test fails, create a Bug and link it to the Test, so developers work from the Bug and the Test shows why it failed.

Step 4: trace and report with links and JQL

Add a link type such as "tests" and "is tested by", link each Test to the stories it covers, and save filters for the views you need, for example project = QA AND labels = regression AND status = Failed. A dashboard with a filter results gadget and a pie chart by status gives a quick picture. The traceability guide covers this in more detail.

Where the no-app setup breaks down

No run history. A Test has one status. When you rerun it next release, the old result is overwritten unless you clone the issue or add sub-tasks per run.
One result per test. Steps share one issue, so you cannot mark step 3 as failed and steps 1 and 2 as passed.
Copied steps drift. Shared steps such as "log in as admin" get pasted into dozens of cases and go stale.
No cycles. Grouping "everything we ran for release 4.2" needs a fix version, sprint or label, and resetting statuses for the next round is manual or needs Automation.
Automated results stay outside. CI test reports do not update Jira without custom scripts against the REST API.
Coverage gaps are hard to see. Finding stories with no linked tests needs manual review or an advanced JQL app.

If you have a short list of manual checks and one or two testers, these limits may never matter. Teams with regression suites, several releases in flight or CI pipelines usually feel them within a few months.

When to add a test management app

A test management app keeps cases, cycles and runs out of your issue list and adds what the no-app setup lacks. Proofline is a Forge-native option: folders, steps with test data and expected results, reusable steps (call one test case from another instead of copying it), test cycles built from a folder or a selection, runs marked pass, fail, blocked or skipped with comments and defect keys, an issue panel showing linked tests and latest results, coverage for any JQL, and CI result import from JUnit, Playwright and Cypress. It can import the CSV you already have, runs entirely on Atlassian Forge, is free for up to 10 users and is pending Atlassian Marketplace review.

Before you choose any app, import 20 of your real cases, run one cycle the size you use in production, and check that the screens stay fast. Already on Zephyr Essential? See how to evaluate Zephyr Essential vs a lighter approach.

Frequently asked questions

Does Jira Cloud have built-in test case management?

No. Jira Cloud has no native test cases, cycles or runs. You can model tests with a custom work type, fields, a workflow and issue links, or add a test management app from the Atlassian Marketplace.

How do I write test steps in a Jira issue?

Use a description template with Preconditions, Steps, Test data and Expected result, or add custom paragraph fields. Test management apps store steps as structured rows so each step can pass or fail on its own.

Can I keep test run history in Jira without an app?

Only with workarounds such as cloning the test or adding a sub-task per run, because an issue has one current status. Test management apps keep every run per cycle.

How do I import test cases from a spreadsheet into Jira?

Save the sheet as CSV and use Jira's built-in CSV import to create one Test per row, or use a test management app that understands multi-row steps and folders.

Should test cases live in the same project as stories?

Usually not. A separate project or board keeps test cases out of sprint reports and velocity, while issue links still connect them to the stories they cover.