Jira Integration
Install the Qualflare app for Jira from the Atlassian Marketplace, pair it with your workspace, and create Jira issues from Qualflare defects automatically.
Jira Integration
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.
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
- Open the Qualflare app on the Atlassian Marketplace and choose Get it now, or install it from Jira → Apps → Explore more apps.
- Approve the permissions. The app asks for the classic Jira scopes
(
read:jira-work,write:jira-work) — Atlassian's tooling requires them for issue creation. - You need to be a Jira site administrator to install it.
Step 2: Pair it with your Qualflare workspace
- In Jira, go to Settings → Apps → Qualflare.
- The page shows a pairing action. Follow it to connect this Jira site to your Qualflare workspace.
- In Qualflare, go to Workspace Settings → Integrations and confirm Jira shows as connected.
You never copy an API token by hand. Pairing exchanges signing keys between Qualflare and the app, and an installation binds to one Qualflare workspace — the first one it pairs with.
Step 3: Configure a project
- Go to Project → Integrations and click Configure on Jira.
- Choose:
- Jira project — where issues are created
- Issue type — Bug, Task, Story, or any type that project accepts
- Priority mapping — which Jira priority each Qualflare severity becomes
- Labels and components — applied to every issue this project files
- Pick the events that should file an issue, then 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.
Qualflare only creates issues. It does not transition, close, reopen, comment on or delete them — your team owns the issue once it exists. An earlier version of this page claimed close and reopen behaviour that never shipped.
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 integrations were disabled, not deleted — your per-project rules are intact. Qualflare shows a Reconnect required notice on the integration. Install the app, pair it, and the existing configuration resumes.
Troubleshooting
"Reconnect required" on the integration card. The app is not paired, or it was uninstalled in Jira. Re-run the pairing in Jira → Settings → Apps → Qualflare.
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.