Using JIRA Software for Test Case Management

Still need help?

The Atlassian Community is here for you.

Ask the community

This article requires fixes

This article has been Flagged for fixing. Use caution when using it and fix it if you have Publisher rights.

For Atlassian eyes only

This article is Not Validated and cannot be shared with customers.

Though Jira Software was not designed to serve as a Test Case Management, it can be configured to support test case management in a couple of different ways.

You can either change its native components (i.e. issue type and workflow) to meet your test case needs, or you can use one of the dozens of apps available in our Atlassian Marketplace. To get an idea of the alternatives available to you, we recommend reading through our documents on integrating Jira  Software with Test Management tools.

The best test case management apps for Jira are found in the Atlassian Marketplace. Here are a couple of our best test management apps: 

The content below was created specifically for Jira 3.x. While much of this information remains accurate for the latest versions of Jira, some aspects may be out of date. Apps in the Atlassian Marketplace represent the easiest approach to test case management.

Jira can also be integrated with a dedicated, third-party test manager or customised to perform lightweight test management as described below:

Option A - Customisation

Because Jira currently offers no direct integration with automated testing frameworks, the preferred approach is to handle automated testing via a continuous integration (CI) server and use Jira primarily for manual testing. You can setup acceptance, integration, functional tests inside Jira.


Some specific features of Jira that are useful for TCM:

  • Link to bugs and requirements
  • Great for manual testing
  • Custom issue types such as test case and user story
  • Multiple affects/fix for versions
  • Automatic and manual issue assignment
  • Workflow controls QA, devs and tester actions
  • Subtasks for manual testing
  • Integrates with source code repository
  • Reporting
  • Issue comments and attachments
  • Customisable
  • Import from other systems
  • Uses an existing and known tool

Only integrates with testing frameworks via CI server - could be addressed by developing your own JIRA plugin
No testing-specific functionality - specific features could be added by developing your own plugin

General Use Case

Using Jira as your test case manager will support these following requirements:

  1. Test cases need to be defined before they can be run.
  2. Changes to the definitions of test cases may be made in parallel for different branches and their releases.
  3. The results of running the test cases have to be accumulated somewhere.
  4. Reports should contain information about many tests run over a period of time on a particular release.
  5. The reports should be easy to update when the underlying information changes, e.g. as ongoing tests pass and fail, or new tests are added and old tests are removed.
  6. The reports should contain a clear summary of the state of the testing activity for each release.
  7. The format of the reports should be such that they can be archived as self-contained collections of files such as test logs.
  8. If a large number of test cases are already defined, then automatic import into the test case manager.

You will need the following tools to customise Jira for internal TCM:

  1. A copy of Jira for you to test with.
  2. A continuous integration (CI) server. This guide will assume that you are using the Atlassian Bamboo CI server as it offers Jira integration.
  3. An automated testing framework able to output tests in a JUnit-compatible format, eg Selenium or JUnit.
  4. Optionally, you may like to store your test plan and internal project documentation in the Confluence wiki. See using Confluence for project documentation.

To proceed, please follow this guide to customising JIRA for test case management.

There is another helpful third party writeup here.

Option B - Integration

If the above features are insufficient then please consider integrating Jira with a dedicated, external test case manager.
Also check out zAgile Teamwork and their great 1, 2, 3, 4 step introduction.


For help or to ask questions, simply post to the community on Atlassian Answers.


While JIRA wasn't designed to serve as a Test Case Management, it can be configured to support test case management in a couple of different ways.


The JIRA platform is, at its core, our workflow engine that allows you to track issues or tasks through a predefined, highly customizable workflow. These tasks can be organized by project, allowing for the entirety of your organization to track their issues at a project level with complete transparency using granular user permissions. In JIRA Software, you are provided with some additional agile functionality, including the ability plan agile work from project backlog to sprint. You'll have fully customizable Kanban and Scrum boards, the ability to estimate time for issues as you prioritize your backlog, and robust reporting features, ranging from burndown charts to velocity measurements. You can either modify its native components (i.e. issue type & workflow) to meet your test case needs, or you can utilize one of the many third party Apps available in our Atlassian Marketplace.

To get an idea of the options available to you, we recommend reading through our documents on integrating JIRA with Test Management tools.

Last modified on Jul 23, 2021

Was this helpful?

Provide feedback about this article
Powered by Confluence and Scroll Viewport.