Jira QA Integration
Connect Evaficy Smart Test with Jira — push defects directly from test runs, keep your issue tracker in sync, and eliminate manual copy-paste between tools.
What Is QA–Jira Integration and Why It Matters
When QA and development use separate tools, defects get duplicated, context gets lost, and fixing bugs takes longer than it should. A tester finds a failure, writes it up in the test tool, then re-enters the same information into Jira by hand — with the risk of missing details, misclassifying severity, or breaking traceability to the original test case.
Integrating Evaficy Smart Test with Jira eliminates that manual step. When a defect is logged during test execution, it can be pushed to Jira in one click — with the title, description, severity, and steps to reproduce already populated. The defect in Evaficy retains a chip showing the Jira issue ID, and clicking it opens the Jira issue directly.
Traceability from test run to Jira issue
Every defect pushed to Jira stays linked to the test run and test case it came from. When a developer fixes the bug, they can follow the link back to see exactly which scenario failed and under what conditions.
What Gets Synced
Not everything in Evaficy is pushed to Jira — only the defect data that belongs in a bug tracker. Test case content, pass/fail results, and run summaries stay in Evaficy where they belong.
Defect title and description
Severity mapped to Jira priority
Steps to reproduce
Link back to the originating test run and test case
Test case content(stays in Evaficy)
Pass/fail results(stays in Evaficy)
Run summaries (these live in Evaficy)(stays in Evaficy)
How to Set Up the Jira Integration
Setup takes under five minutes. You need your Atlassian domain, a Jira API token, and the project key for the Jira project that will receive defects.
Go to Project Settings → Integrations tab
Open your project in Evaficy Smart Test, navigate to Project Settings, and select the Integrations tab. Each project has its own Jira integration settings.
Enter your Atlassian domain
Enter your company's Atlassian domain in the format yourcompany.atlassian.net — without https:// or a trailing slash. This is the subdomain you use to access Jira in your browser.
Enter your account email and Jira API token
Use the email address of your Jira account and generate an API token from your Atlassian account security settings. API tokens are more secure than passwords and can be revoked independently.
Enter your Jira project key
The project key is the short prefix used on Jira issue IDs — for example BUG, ENG, or QA. You can find it on the Jira project board or in the URL when viewing issues. Keys are case-sensitive.
Click Test Connection to verify
Evaficy validates your credentials and project key against the Jira API. A successful test shows your account name, confirms the project was found, and lists the available issue types in that project.
Save
Once the connection test passes, save the integration. Your project is now connected — any defect can be pushed to Jira from that point on.
Generating a Jira API token
Go to id.atlassian.com → Security → API tokens → Create API token. Give it a descriptive name like "Evaficy integration". Copy the token immediately — Atlassian only shows it once. Store it somewhere secure before saving it in Evaficy.
Pushing a Defect to Jira
Once the integration is configured, pushing a defect to Jira is a single action from within the defect detail view. Open a defect logged during a test run, click Push to Jira, and Evaficy creates the issue in your Jira project automatically.
After the push succeeds, the defect shows a linked chip displaying the Jira issue ID (for example, BUG-142). Clicking the chip opens the Jira issue directly in a new tab. The link is permanent — it stays on the defect even if the Jira issue is updated or reassigned.
Push once, not repeatedly
Each defect can only be pushed to Jira once. If you need to update the Jira issue after the initial push, make changes directly in Jira. Evaficy reflects the link but does not sync subsequent edits bidirectionally.
Issue Type Selection
Jira projects support different issue types depending on how your team has configured them — Bug, Task, Story, and so on. Evaficy discovers the available issue types automatically when the connection is tested and selects the most appropriate one at push time.
The selection priority is: Bug → Task → Story → first available type. If your Jira project has a Bug type, defects will always be created as Bugs. No manual configuration of issue type mapping is required.
Severity to Priority Mapping
Evaficy defect severity is mapped to Jira issue priority automatically on push. The mapping follows a direct one-to-one translation so that priority in Jira accurately reflects the severity assigned during test execution.
Common Setup Errors
Most connection failures fall into three categories. The Test Connection button surfaces the specific error so you can fix it without guessing.
Wrong project key
Test Connection will list the project keys available in your Jira account. Pick the correct one from that list.
Expired API token
Regenerate your API token in Atlassian account settings (id.atlassian.com → Security → API tokens). Update the token in Evaficy and test the connection again.
Domain format error
The domain must be yourcompany.atlassian.net — no https://, no www., no trailing slash. Double-check the format if the connection test fails immediately.
Related guides
Defect Reporting Guide
How to write defect reports that developers can act on — structure, severity, evidence, and reproduction steps.Test Run Execution Guide
Step-by-step execution tracking, defect logging in context, and interpreting run results accurately.Test Plan Management
How QA teams use structured test plans to scope releases, track execution coverage, and ship with confidence.Connect your test runs to your bug tracker
Push defects from test execution directly to Jira — no copy-paste, no lost context, full traceability from test case to issue.
Start your trial