Jira Test Case Management: The Complete Workflow Guide

Many Agile teams keep testing with Jira, but Jira lacks test runs and test reports. That is why teams compare Jira test management tools. This guide reviews the best test management tools for Jira in 2026 and shows a Jira test case management workflow with the Testomat.io Jira plugin. See all features of the Jira workflow integrated with our test management system.

What Is Jira in Testing?

Jira is an Atlassian tool for planning and tracking work in Agile software development. Teams use it to track issues and automate workflows.

In testing, Jira is where QA teams log bugs and link test cases to user stories. Jira can hold test cases. Running and reporting on them needs a plugin. A Jira test management plugin adds these features.

Atlassian built Jira as a project management tool. Its main job is planning and tracking work. Today, Marketplace add-ons give QA teams a Jira testing tool inside the same workspace. The Atlassian Marketplace lists over 200 testing apps for Jira, so picking a Jira test tool takes some research.

Jira Software is a commercial product. Atlassian offers a free Jira Cloud plan for up to 10 users with 2 GB of storage and community support only. Paid plans add more users and storage. You can find plan details on the official Jira website and ask questions in the Atlassian Community.

Key Jira Concepts for Testers

Jira issues. This is the general term for any work item in Jira. Teams use five common Jira issue types:

• Epic: a large piece of work that usually spans several sprints.
• User Story: a part of an epic that the team completes within one sprint. It describes a feature from the end user’s point of view.
• Task: a small technical job that one specialist completes.
• Sub-task: a part of a task with the smallest unit of work.
• Bug: a defect in the app that the team needs to fix.

Jira project. A set of issues the team completes to reach a goal. You can configure assignees and workflows for each project.

Agile boards. A visual view of the team’s workflow. Jira offers Scrum and Kanban boards. They split large projects into smaller blocks and show where each piece of work stands.

Can You Use Jira for Test Case Management Without a Plugin?

Yes, at a basic level. Many teams start testing with Jira by creating a custom issue type called Test. They add statuses such as Passed and Failed to its workflow. This is the basic test case management Jira offers out of the box.

Advantages of this approach:

• You can link a test to several user stories and bugs, so the team can reuse test cases.
• Testers create test cases the same way they create any other Jira issue.

Limits of test case management in Jira without a plugin:

• Lost run history. When a tester changes the status, Jira overwrites the previous result.
• Manual reruns. Completed issues move to Done. For regression testing, you create a new sub-task for each rerun.
• One result per test. Test steps share a single issue, so the result covers the whole test.
• Missing test suites and test plans. Checks stay as separate issues outside a planned run.
• Shared reports. Runs live as sub-tasks of one issue, so reports combine all runs.
• Separate automated results. Results from your test frameworks stay outside Jira.

Using Jira for test case management this way works for a small team with a short list of manual checks. For regression cycles and test automation, you need one of the test management tools Jira supports through the Marketplace or a direct integration. We compare both options in detail in Test Cases in Jira vs Testomat.io.

Two Types of Jira Test Management Tools

Before you pick a test management tool Jira users will open every day, decide which type fits your team. Atlassian test management apps fall into two groups.

Jira-native apps

These apps install from the Atlassian Marketplace and store tests inside Jira, often as Jira issue types. Xray, Zephyr, QMetry and AIO Tests work this way.

• Strengths: testers stay inside Jira. Tests appear on boards, and you can search them with JQL.
• Limitations: test data adds volume to your Jira instance. Licensing is the bigger factor. Atlassian requires each Marketplace app to match the user tier of your Jira site, even if only a few people use the app. If your Jira site has 500 users and 15 testers, you pay the app price for 500 users.

Test management systems with Jira integration

These are separate platforms built for testing. They connect to Jira through a plugin and an API. Testomat.io, Testmo and PractiTest work this way.

• Strengths: a test repository built for testing and deeper reports on automated tests. Licensing goes per tester seat. Jira users see test data inside their tickets through the plugin.
• Limitations: the team adopts a second tool. The quality of the Jira integration decides how comfortable daily work feels.

Best Test Management Tools for Jira in 2026

The list below covers both types of test case management tools Jira teams use. It focuses on tools with an active Jira integration in 2026. Note that Tricentis retired its Test Management for Jira app on October 6, 2025. Existing installs still get support, but new purchases are closed.

1. Testomat.io: Jira Test Management Tool for Manual and Automated Tests

Type: test management system with a two-way Jira plugin.

Testomat.io keeps manual and automated tests in one repository and syncs them with Jira in both directions. Testers link tests, suites and plans to Jira issues. Product owners see linked tests and run results on the issue itself.

Key features:

• Create tests and suites from a Jira issue, or bulk-create tests from a list of titles
• Run manual tests from the issue and start automated tests in CI
• Combine manual and automated tests in one Mixed Run
• Create Jira bugs from failed tests with steps and a run link added
• Track coverage per user story and per sprint, including the automation percentage
• Edit BDD feature files from Jira and work in test branches named after the issue
• Use AI to suggest tests for a suite and improve test descriptions
• Import test cases from TestRail or Xray
• Read-only view of linked tests for all Jira users

Best for: teams with a large share of automated tests and teams where non-technical people follow testing in Jira.

2. Xray

Type: Jira-native app.

Xray stores tests as Jira issue types and manages manual and automated tests inside Jira. Teams customize screens, fields and workflows the same way as for other Jira issues.

Key features:

• Uses Jira issue types to specify, plan and execute tests
• Agile board enhancements show the testing status of each story
• BDD with Cucumber, so non-technical users can take part in automation
• Integrates with Cucumber, Robot Framework, JUnit and Jenkins
• Built-in gadgets and reports for traceability and coverage
• Xray Enterprise adds test case versioning and lets teams trigger automated tests from Jira

Best for: teams that want testing to live fully inside Jira and accept Jira-tier licensing.

3. Zephyr (formerly Zephyr Scale)

Type: Jira-native app by SmartBear.

SmartBear renamed Zephyr Scale to Zephyr. The app targets growing teams that need structured, reusable test libraries inside Jira.

Key features:

• Organizes large test case libraries in folders and test suites
• Reuses test cases across projects
• Tracks test executions in test cycles
• Links test cases to user stories and shows progress inside Jira
• AI-powered suggestions for test steps
• Records and replays test executions for no-code automation

Best for: mid-size and large teams that need structured, reusable test libraries inside Jira.

4. Zephyr Essential (formerly Zephyr Squad)

Type: Jira-native app by SmartBear.

Zephyr Squad now appears on the Marketplace as Zephyr Essential. It adds a test panel inside each Jira issue and covers basic test management.

Key features:

• Test panel inside each Jira issue
• Manual and automated testing inside Jira
• BDD support with Cucumber
• Uses Jira components, labels and your existing boards
• Project reports and dashboard gadgets

Best for: small Agile teams that start with simple pass/fail tracking in Jira.

5. QMetry Test Management for Jira (QTM4J)

Type: Jira-native app by SmartBear.

QMetry brings enterprise test management into Jira for Agile and DevOps teams. It can migrate test cases from other Jira testing apps, so teams keep their existing tests.

Key features:

• Test case management with test cycles for execution
• BDD support with Gherkin
• Exploratory test recording and defect logging
• Automation support with tools such as QAF and SpecFlow
• Migration of test cases from other Jira testing apps
• Test reports generated from test cycles

Best for: enterprise teams that need test cycles and reports inside Jira.

6. AIO Tests

Type: Jira-native app.

AIO Tests is an all-in-one testing app inside Jira. It links test cases with requirements and defects across projects.

Key features:

• Test cases, test sets and test cycles inside Jira
• Cross-project traceability from requirements to defects
• Extra custom fields for test cases and workflows
• Test cycles organized in folders for release testing
• Integrations with Cucumber, TestNG and Jenkins
• AI-assisted test creation

Best for: teams that want cross-project traceability without leaving Jira.

7. TestFLO

Type: Jira-native app by Deviniti.

TestFLO builds testing from Jira issue types and works with any Jira issue type as a requirement or defect. It targets Jira Data Center. For Jira Cloud, Deviniti offers a migration path to its RTM app.

Key features:

• Test repository of Test Case Templates in a folder tree
• Test Plans created from repository folders
• Custom fields and workflows like any native Jira issue
• Automated test triggers from Jenkins and Bamboo
• REST API for test automation
• Traceability from requirements through test cases to bugs

Best for: Data Center teams with a mature, customized QA process.

8. QAlity Plus

Type: Jira-native app.

QAlity Plus focuses on collaboration between testers, developers and product managers. Testers create test cases directly inside existing Jira issues.

Key features:

• Test cases created inside existing Jira issues
• Import and export of tests
• Test execution in Jira with failed steps marked
• Test cycles with JQL to select tests
• Execution and traceability reports inside Jira

Best for: small teams that want light test management in the issue view.

9. Testmo

Type: test management system with a free Jira add-on.

Testmo combines manual test cases with exploratory sessions. It also reports on test automation from CI pipelines.

Key features:

• Manual, exploratory and automated tests in one platform
• Jira Cloud and Jira Data Center support
• Jira’s Create Issue page inside Testmo, with your Jira fields
• Free Jira add-on for extra integration
• Reports, metrics and charts for testing activities
• Integrations with GitHub, GitLab and CI pipelines

Best for: teams that rely on exploratory testing alongside test cases.

10. PractiTest

Type: test management system with a free Jira add-on.

PractiTest manages manual and automated tests in one tool and syncs data with Jira.

Key features:

• Data sync between PractiTest and Jira
• Field mapping between the two tools
• Bug reports created during testing and synced to Jira
• Reuse of test data across both tools
• Free Jira add-on for extra integration

Best for: teams that need custom field mapping between Jira and their test tool.

Jira Test Management Tools Comparison Table

The table compares the best Jira test case management tools on the points that change your daily work.

How to Choose the Best Test Case Management Tool for Jira

Which is the best test case management tool for Jira? It depends on your stack and on the share of automated tests. Check these points before you start a trial of any Jira test case management software:

• Manual vs automated tests. If most of your tests run in CI, pick a tool that imports results from your frameworks and links them to user stories.
• Who pays for access. Count your Jira users and your testers. A Jira-native app charges for the whole Jira site. A test management system charges for the people who write and run tests.
• Jira hosting. Check that the tool supports your Jira Cloud or Jira Data Center setup.
• Traceability. Product owners should see test status and coverage on each user story.
• BDD support. If your team writes Gherkin scenarios, check how the tool edits and runs feature files.
• Migration. If you already use a tool, check the import path for your existing test cases.

A simple rule: a small team with mostly manual tests can start with a Jira-native app. A team with large automated suites in CI will get more from a test management system with a strong Jira test management plugin.

Free Test Management Tools for Jira

Small teams can test with Jira at a low cost:

• Custom Jira issue types. Free on any Jira plan, with the limits described above.
• Marketplace apps for small sites. Atlassian Marketplace apps price the first tier (up to 10 users) at a flat rate. Some vendors, including Deviniti, make their cloud apps free for teams of up to 10 users.
• Testomat.io Free plan. Free for 2 users and 2 projects, with support for automated tests. The Jira plugin needs the Professional plan, which you can try for free first.

Benefits of a Test Management Tool for Jira

A Jira integration brings testing data into the tool your team already uses. These benefits explain why many teams look for the best test management tool for Jira:

1. Non-technical specialists join testing. With a two-way integration, product owners and analysts follow test progress in Jira. They stay in one tool.
2. Better test reporting. Run results and coverage appear on each Jira issue. The team finds and fixes bugs faster.
3. Shorter time to market. Teams run automated tests from Jira and see results next to the user story. Developers and testers spend less time on status updates.

Many of our clients run their projects in Jira. This prompted our team to build a two-way integration between Testomat.io and Jira.

How to Start Test Management for Jira with Testomat.io

This section shows how to build a Jira testing process with Testomat.io. Developers learn about defects on time, and testers control bug fixes from one place.

Start From an Example Project

Our team has prepared guides on how Testomat.io works with popular test frameworks: Cucumber, Playwright, WebDriverIO and others. Check our demo projects for a quick start. Below, we focus on how to connect Jira to Testomat.io.

Connect Jira and Testomat.io in 6 Steps

#1 Install the Testomat.io Jira plugin

Install the Testomat.io Jira plugin from the Atlassian Marketplace:

1. Open your Jira site as an administrator.
2. Open the Apps menu and search the Marketplace for Testomat.io.
3. Select the Testomat.io app and click Get app.
4. Wait until the installation completes.

#2 Create a Jira project

Click Create in the Jira toolbar and complete the project fields. Note the project identifier. You will find it at the end of the project URL.

#3 Generate a Jira API token

Open your Atlassian account, go to the API tokens section and click Create API token. Add a label and click Create. Copy the token, since you will paste it into Testomat.io in the next step. Atlassian explains the process in Manage API tokens for your Atlassian account.

#4 Connect Testomat.io to the Jira project

In your Testomat.io project, open the Jira Integration menu. Enter the Jira project URL and your Jira username. Then add the API token and the Jira project ID. Click Save.

#5 Check the connection

Click Test Connection to test Jira access. A green pop-up confirms that Testomat.io can reach Jira. Run this check before you link any tests.

#6 Start working with the plugin

After the sync, your team gets these Jira test management features:

• Create tests and suites from a Jira issue and edit them in Jira.
• Link manual and automated tests to Jira issues.
• Run manual tests from the issue as a checklist.
• Run automated tests in CI from Jira.
• Edit BDD feature files from Jira.
• Create Jira issues for failed tests and runs.
• Work with test branches from Jira.
• Check test priority and tags on each issue.
• Track user story coverage and sprint coverage.
• Show tests on Confluence pages with macros.

The Jira Integration page lists every feature of the plugin. Below, we focus on the test management Jira features a QA lead or test manager uses daily.

Jira Test Case Management Workflow in Testomat.io

Here is a typical Jira test case management workflow with Testomat.io, from writing tests to closing bugs.

Create Test Cases in Jira

Test case creation in Jira happens in the plugin panel on the issue. Add a single test, or paste a list of titles to create tests in bulk. Testomat.io saves them in the test repository and links them to the issue.

Link Test Cases to Jira Issues

You can also link existing tests, suites and plans to a Jira issue. One test can cover several issues, and one Testomat.io project can connect to several Jira projects. To link a test from Testomat.io:

1. Open the project.
2. Find the test.
3. Select Link to Issue from the menu.
4. Enter the key of an existing Jira issue or create a new one.

Once linked, the test appears on the Jira issue. If someone deletes the issue, Testomat.io removes the link.

Create Jira Issues for Failed Tests and Runs

Open a run with a failed test and create a new Jira issue for it, or link an existing one. Testomat.io adds the steps and a link to the run report. You choose the issue type and priority before you save. After the fix, re-run the linked tests to confirm it.

Run Tests Directly From Jira

With the plugin, teams testing Jira user stories run tests from the ticket they already have open:

• Manual runs: execute linked tests as a checklist inside the issue.
• Multi-environment runs: run the same manual tests separately for each environment.
• Automated runs: start linked automated tests in your CI pipeline.
• Mixed Runs: start automated tests in CI and check manual tests in Jira at the same time. Testomat.io merges both into one result.

Work With Branches in Jira

Testers can create test branches named after the Jira issue and switch between a branch and Main. This keeps test changes for a feature separate until the feature ships.

Traceability and Test Coverage in Jira

The plugin adds test reporting to Jira. On the Coverage page, users see the following for tests linked to user stories:

• Counts of passed, failed and skipped tests.
• The automation percentage.
• Which linked tests are manual and which are automated.
• Test execution history in the Runs tab, with status, type and environment.

Testomat.io also posts a run summary to the linked Jira issue. Sprints Coverage shows tests per sprint, so managers can report progress to stakeholders.

Jira Statistics in Testomat.io

The integration works in both directions, so you can also see Jira data in Testomat.io. The Jira Statistics widget shows test results for each linked issue, with passed, failed and skipped counts. If one Testomat.io project links to several Jira projects, the widget covers all of their issues.

This makes test management in Jira visible to developers and managers.

Running Tests on CI/CD From Jira

Testomat.io integrates with CI/CD tools such as GitHub Actions, GitLab CI, Azure DevOps, Jenkins and CircleCI. Jira users who connect Testomat.io can start automated runs on CI from the same workflow.

For Agile teams, this matters. Automated Jira tests catch errors early in development. The team saves time, and the client saves budget.

Conclusion

Jira is a strong base for Agile work, but it needs a plugin for real test management. Jira-native apps keep everything inside Jira and charge for every Jira user. Test management systems with a Jira integration give deeper automation support and charge for testers only.

If you want to keep Jira as your main workspace and manage manual and automated tests together, try Testomat.io as your Jira test management tool. Your team writes test cases, runs test cycles and gets reports without leaving Jira.

Prefer video? Watch the setup steps below 👀