# Jira Integration

Source: https://docs.qualflare.com/docs/integrations/jira · Last updated: 2026-11-10

Connect Jira Cloud with the Qualflare app for Jira and a pairing code, then file Jira issues automatically from Qualflare defects and test failures.

Qualflare creates Jira issues from your test failures, so defects land in the same
backlog as the rest of your engineering work.

Issues are created by the **Qualflare app itself**, not by a person's Jira account. The
connection does not break when whoever set it up changes role or leaves.

> **Warning:** Jira **Cloud** only. Atlassian stopped accepting new Marketplace apps for Data Center,
> so there is no Data Center version.

## Setup

### Step 1: Install the app in Jira



The Qualflare app for Jira is not public on the Atlassian Marketplace yet. If you want to try
it, message us in the in-app chat or email [support@qualflare.com](mailto:support@qualflare.com).

1. Install the app as a **Jira site administrator**. Only a site administrator can install
   the app.
2. Approve the permissions. The app asks for the classic Jira scopes
   (`read:jira-work`, `write:jira-work`), which Atlassian marks as current for the endpoints
   it calls. The finer-grained alternatives are still in beta.

### Step 2: Pair it with your Qualflare workspace

Pairing starts in Qualflare, continues in Jira and finishes back in Qualflare. You need a
Qualflare workspace role of **Editor** or higher, and you must be a Jira site administrator.

1. In Qualflare, open **Integrations** in the workspace sidebar, find **Jira** under
   **Testing** and click **Install**. The **Connect Jira** dialog opens.
2. Click **Get a pairing code**. The code has 8 characters, shown as `XXXX-XXXX`. It works
   once, for 10 minutes, and only for you and this workspace.
3. In Jira, go to **Jira settings** > **Apps** > **Qualflare Test Management for Jira**. Type the code
   into **Qualflare pairing code** and click **Connect to Qualflare**.
4. A Qualflare tab opens. Check that the **Workspace** and the **Jira site** are right,
   select the confirmation box (`Connect <site> to <workspace>`), then click **Connect Jira**.

After 5 wrong codes, you can't get a new code for that workspace for 15 minutes.

You never copy an API token by hand. Pairing exchanges signing keys between Qualflare
and the app. A workspace connects to one Jira site, and an installation binds to **one**
Qualflare workspace — the first one it pairs with — until a Jira site administrator clicks
**Disconnect** on the app's page in Jira, or the Jira integration is removed in Qualflare.

> **Caution:** Don't click **Reconnect to Qualflare** in Jira while the connection works. It replaces the
> site's signing key at once, and the current connection stops delivering. Qualflare can't
> pair a workspace that already has Jira, so the only fix is to remove the integration, which
> deletes every project's Jira settings, then pair the app again and set up each project.

### Step 3: Configure a project

1. In the project sidebar, open **Integrations** and click **Configure** on Jira.
2. Choose:
   * **Project** — where issues are created
   * **Issue Type** — Bug, Task, Story, or any type that project accepts
   * **Priority** — **Auto (from severity)**, or one fixed priority from Highest to Lowest
   * **Priority Mapping** — with Auto, which Jira priority each defect severity becomes
   * **Labels** — applied to every issue this project files
3. Under **Events**, pick the events that should file an issue, then click **Save**.

## What creates an issue

| Qualflare event     | What Jira gets                                   |
| ------------------- | ------------------------------------------------ |
| Defect created      | A new issue titled `[Defect #12] <defect name>`  |
| Launch failed       | An issue naming the launch and its failure count |
| Cluster created     | An issue for a new failure cluster               |
| Flaky test detected | An issue for the test that flipped               |

Each event is opt-in per project, so a project can file issues for defects only.

The description carries the defect's severity, environment, category, status, team and
root causes when they are set, followed by the description and the expected/actual
results.

> **Note:** Qualflare only **creates** issues. It does not transition, close, reopen, comment on or
> delete them — your team owns the issue once it exists.

## Already using the API-token setup?

Older Jira connections used a personal API token. That method is retired: it carried one
person's full Jira permissions and died with their account. Those connections were
disabled, and their card shows **Reconnect**.

> **Caution:** Moving to the app deletes your project Jira settings. Qualflare can't pair a workspace
> that still has a Jira integration, even a disabled one, so you have to remove the old one
> first. Removing it deletes every project's Jira configuration. The card says "Reconnect
> required — remove it and install it again."

1. Write down each project's Jira settings. A disabled integration doesn't appear on a
   project's **Integrations** page, so first click **Enable** on the Jira card in
   **Workspace → Integrations**. Then, in each project, open **Integrations** and click
   **Edit** on Jira. For an old connection, **Project** and **Issue Type** show no value,
   because Qualflare can't list your Jira projects until the app is paired. Take the
   project key and issue type from an issue Qualflare filed in Jira earlier.
2. In **Workspace → Integrations**, click the trash icon on the Jira card, then **Remove**.
3. Install the app and pair it (Steps 1 and 2 above).
4. Configure each project again (Step 3).

## Troubleshooting

**"Reconnect" on the integration card.** The app was disconnected or uninstalled in Jira,
or this is an old API-token connection. Pairing again fails while the old integration
exists, so you have to remove it first.

> **Caution:** Removing Jira deletes every project's Jira settings. Write them down first, as in step 1
> of **Already using the API-token setup?** above.

Then remove the integration, and install and pair the app again, as in **Already using
the API-token setup?** above.

**Issues are not being created.** Open **Project → Integrations → Recent deliveries**.
Every attempt is recorded there with its outcome, and a failed one names the reason —
for example a Jira project the app cannot post to, or a required custom field the issue
type demands.

**The Jira project list is empty.** The app reads projects with the permissions granted
at install. If a project is restricted, grant the Qualflare app access to it in Jira.

## See Also

* [Integrations Overview](https://docs.qualflare.com/docs/integrations)
* [Defects](https://docs.qualflare.com/docs/defects)
* Changelog: [Qualflare Test Management for Jira, now on the Atlassian Marketplace](https://changelog.qualflare.com/jira-cloud-marketplace-app)
