← All posts

Test Management

Jira test case management without Jira issues

Keep test cases out of Jira's issue list, link them to stories both ways, and send automated results back to the ticket with Qase.

Qase Team

Qase Team

Nov 7, 20268 min read
A stack of layered sheets linked by glowing threads to a structured grid of cubes, representing Jira issues connected to organized test cases

Most teams that ask about test management in Jira already have years of work in Jira. The stories are there, the bugs are there, and so are the sprint boards and the release versions. Putting test cases there too seems like the obvious next step. Then a few months later the project has 4,000 extra issues, the backlog filters need a "not a test" clause, and everyone who wants to read a test run needs a license for a Jira app.

There's another way to set it up. Keep the test cases, runs and results in a test management tool, and link them to the Jira issues they cover. This guide shows how that works with Qase. It covers linking from both sides, sending automated results back to the ticket, defects that sync status with Jira, and a plain list of what the integration doesn't do.

Is Jira a test management tool?

Jira tracks work items like stories, bugs and tasks, and it has no built-in object for a test case, a test run or a test result. So on its own, it isn't a test management tool. Teams fill the gap in one of two ways: a Marketplace app that stores tests inside Jira, or a separate test management tool that links to Jira.

The two best-known apps of the first kind take different approaches:

  • Xray makes tests Jira issues. Tests, preconditions, test sets, test plans and test executions are all issue types, so JQL, boards and Jira dashboards work on them.
  • Zephyr keeps test cases inside the Jira UI as its own records, which aren't Jira issues, so JQL doesn't search them. (The older Zephyr Squad did use a Test issue type.)

If your team wants to query tests with JQL and put them on a board, Xray does that well, and it's a reasonable choice.

Both apps are billed on your Jira user tier, the way most Marketplace apps are. If Jira has 400 users and 12 of them are testers, you pay for 400. For a company where the whole engineering org lives in Jira, that's often the line item that starts the conversation about a separate tool.

What a standalone tool linked to Jira looks like

Test cases, test runs and defects live in the test management tool. Jira issues carry links to them, and a panel inside the issue shows what's linked.

For Qase, the Jira side is a free Marketplace app called Qase for Jira Test Management. On Jira Cloud it's built on Atlassian's Forge platform. Self-hosted Jira (Server and Data Center) uses a separate integration.

Setup takes a Jira admin and a Qase workspace owner or admin (or one person who is both):

  1. In Qase, go to Integrations, find Jira Cloud and click Install now. Qase sends you to the Marketplace listing.
  2. Click Get it now, choose your Jira site and approve the permissions.
  3. In Jira, open the app settings (Settings, then Apps, then Qase for Jira), enter your Qase URL (usually app.qase.io) and click Connect with Qase.
  4. Authorize in the Qase tab that opens. Jira confirms the connection and names the workspace.

Each Jira site connects to one Qase workspace. If you don't want Qase reading every Jira project, turn on access control from the Jira Cloud card in Qase and pick the projects it can see. With access control off, it can see all of them.

Linking test cases to Jira issues, both ways

Links can be made from either side, and they show up on both.

From Jira. Open an issue and you'll see two panels. The one labeled Qase sits in the details column and lists linked test cases. The one called Linked Qase test runs sits in the main column and lists runs. Click + Link a test case or + Link a test run, search by title or ID, and pick the result. An issue can have as many cases and runs as you want.

From Qase. There are three places to link an issue:

  • A test case: the Properties tab in the case preview. For many cases at once, select them and use Edit to bulk-link.
  • A test run: External Issues on the run dashboard.
  • A defect: the "Link with apps" section in Defects.

Who sees the links depends on Jira permissions. People need Browse projects to see linked cases and runs, and Edit issues to add or remove them. Without Edit issues, the link buttons are hidden. So if one person sees an empty panel and a colleague doesn't, check permissions and access control before assuming the sync broke.

Pushing automated results back into Jira

This is the part Xray and Zephyr handle natively, since the results already live inside Jira. With a standalone tool, you link each automated run to the Jira issue it tested. Then the run shows up in that issue's Linked Qase test runs panel, along with its pass/fail.

Every Qase reporter can set the link when it creates the run. In the JavaScript reporters (Playwright, Cypress, Jest and others), it's testops.run.externalLink:

testops: {
  project: "SHOP",
  run: {
    title: "PR checks",
    externalLink: { type: "jiraCloud", link: "SHOP-1234" },
  },
},

Use jiraServer instead of jiraCloud for self-hosted Jira.

Hardcoding a key only helps for a one-off run. In CI you want the key to come from the work itself, and the branch name is usually the easiest place to get it. If your team names branches like SHOP-1234-saved-cards, this GitHub Actions step pulls the key out and passes it to the reporter as an environment variable:

- name: Link this run to the Jira issue
  if: github.event_name == 'pull_request'
  run: |
    KEY=$(echo "${{ github.head_ref }}" | grep -oE '[A-Z][A-Z0-9]+-[0-9]+' | head -1)
    if [ -n "$KEY" ]; then
      echo "QASE_TESTOPS_RUN_EXTERNAL_LINK={\"type\":\"jiraCloud\",\"link\":\"$KEY\"}" >> "$GITHUB_ENV"
    fi

- run: npx playwright test
  env:
    QASE_MODE: testops
    QASE_TESTOPS_API_TOKEN: ${{ secrets.QASE_TOKEN }}
    QASE_TESTOPS_PROJECT: SHOP

QASE_TESTOPS_RUN_EXTERNAL_LINK takes the same JSON as the config option. If the branch has no key, the step sets nothing and the run reports without a link, which is what you want for a branch like fix-typo.

Teams that use pytest, JUnit or another framework have the same option in that reporter's config. If you upload JUnit XML with the Qase CLI instead of using a reporter, add the issue to the run under External Issues, or do it through the Qase API.

The reviewer of that pull request can now open the Jira issue and see which tests ran against it and how they did, without opening CI.

Defects, status sync and traceability

When a result fails, you can file the defect from the run without switching tools.

Mark the result as Failed (or Blocked, or Invalid), create a defect, and under Choose Integrations pick Jira Cloud. You can create a new Jira issue from there, or link one that already exists if someone filed the bug first.

Statuses sync in both directions. When the Jira issue moves to a done status, Qase marks the defect resolved. It works the other way too: when you change a defect's status in Qase, you pick the status the linked Jira issue moves to. The mapping is set per Qase project and per Jira issue type, with a Default entry for any issue type you haven't mapped. If your projects share a workflow, Copy to projects applies one mapping to the rest, matching statuses by name.

Traceability comes from the links you've already made. Once your stories have test cases linked to them, the Requirements Traceability Matrix in Qase shows which requirements are covered and connects each one to its test results. That's the report people usually want when they ask whether the release was tested, and it comes from links your team made while doing the work.

What the integration doesn't do

A standalone tool has trade-offs, and it's better to know them before you pick one:

  • Test cases aren't Jira issues. You can't run JQL on them, put them on a Jira board or move them through a Jira workflow. If your team relies on any of those, that's a real reason to look at Xray.
  • Defects start in Qase. You can link a Qase defect to a Jira issue from Qase, but you can't create a Qase defect from inside Jira.
  • Reports live in Qase. The Jira panels show links and run results, and that's all they show, so a Jira dashboard can't chart coverage.
  • It's a paid feature. The Free plan doesn't include integrations, so Jira needs the Teams plan or higher. Teams has a 14-day trial with no credit card, which is enough time to connect a site and link a sprint's worth of stories.
  • One workspace per Jira site. A Jira site connects to one Qase workspace at a time. There's a "Copy installation" option for adding a second workspace, but the settings don't sync between them afterwards.

If none of those are dealbreakers, you get test cases that don't clutter Jira, and test results people can see from the Jira issue they're already looking at. Every story still shows what was tested against it.

Further reading: Qase Jira integration | Requirements traceability matrix | Don't put off traceability | Defect management | Jira Cloud setup docs

Ship quality software faster with Qase