Jira is a proprietary issue-tracking product developed by Atlassian that allows bug tracking and agile project management.
Qase offers a robust integration with Jira, enabling you to link test cases, test runs, and defects to Jira issues both, from Qase, and from Jira.
The statuses of a Qase defect and its linked Jira issue are synchronized. When a Jira issue is set to a completed status, the corresponding Qase defect is marked as resolved, and vice versa.
Installation
🏢 If you are using Jira Data Center, you can install the app from Jira Marketplace instead of using the package provided in this article. Once you do so, proceed directly to step 5 of this instruction.
🔒 If your Jira server routes outbound traffic through a forward proxy, see Proxy Configuration below and complete those steps before proceeding to step 5. Without it, the authorization will fail.
Download the plugin package attached at the end of the article.
Go to “Manage apps” page in Jira:
Select the plugin package you’ve downloaded, and click “Upload”.
After installation, click the “Configure” button and link Jira with Qase:
You will be re-directed to Qase, click “Authorize” on the this step.
That’s it, you’re ready to go!
Proxy Configuration
During installation, the plugin makes a single outbound call from your Jira server to https://app.qase.io to complete authorization. If your Jira server sits behind a corporate proxy, you’ll need to configure it using one of the methods below.
**Option 1 - JVM system properties (recommended)
Add the following to $JIRA_INSTALL/bin/setenv.sh via JVM_SUPPORT_RECOMMENDED_ARGS:
-Dhttps.proxyHost=proxy.example.com
-Dhttps.proxyPort=3128
-Dhttps.proxyUser=user # optional
-Dhttps.proxyPassword=pass # optional
-Dhttp.nonProxyHosts="localhost|`*.internal`" # optional, pipe-separated, * wildcard
This is the standard Atlassian-recommended approach for Jira.
Option 2 - Environment variables
Export these in your Jira service environment:
HTTPS_PROXY=http://user:[email protected]:3128
NO_PROXY=localhost,.internal # optional, comma-separated, suffix match
Lowercase variants (https_proxy, no_proxy) are also supported.
Basic auth credentials can be embedded in the URL.
**Precedence: If both options are configured, JVM system properties take priority over environment variables.
**Note: Only HTTPS traffic is proxied. HTTP_PROXY is not supported because the plugin exclusively calls https://app.qase.io.
Mapping Statuses Between Qase and Jira
Qase Defects have the following statuses: Open, In-progress, Resolved, Invalid
To map the statuses, click on the app card, and then, choose “Settings” from the (–) menu.
You might have several projects ¹ in your Jira instance, each with different and potentially unique statuses for each issue type ²
Select the Project, Issue Type and click on “Add transition” and select the Defect Mapping and Save the changes:
You have an option to “Do nothing” in terms of status update of a Qase defect, once the associated Jira issue gets transitioned into a specific status - then, the Qase defect will remain in the status it was.
Link from Qase
1. Link Jira issues to Qase Test cases
In your repository, click any test case to open its preview and switch to the Properties tab.
Scroll down to the “Link with Apps” section, and choose Jira Server. Then, proceed to search and link your issues.
Linked issues can be removed with the ( x ) icon.
Unlink a test case.
2. Link Jira issues to a Qase Test run:
Test runs can be linked to a Jira issue, from the Run Dashboard.
Under the “External Issues” section, click ‘Select an Integration’ to proceed. Only one Jira issue can be linked to the Test run.
The option to link Jira issue can be found in the Test run Dashboard, under External Issues.
3. Link Jira issues to a Qase defect:
a) From Test runs
If you encounter a defect during a test run, you can either create a new Jira issue directly from Qase or link an existing Jira issue.
In the test run, mark your case as Failed, Blocked, or Invalid and proceed with creating a Defect.
In the Defect creation form, under “Choose Integrations” select “Jira Server” and click “Add defect”
creating a **new Jira issue** from a Qase Test run
Linking an **existing Jira issue** from a Qase Test run
b) From Defects
If you’re creating a defect that isn’t linked to any result from the defects section, you can link a Jira issue from the defect dashboard using the “Link with apps” section.
Linking a Qase defect to a Jira issue
Once linked, the defect will be visible under the External column in the Defects section of your project.
And, also in the defect dashboard here -
Once a Defect has been created and if you update the status of the Defect, you’ll notice that you have the option to select the status for the associated Jira issue to be transitioned into:
Link from Jira
1. Test cases
Click “Link a case”
Insert test case title or its Case ID into the field and click “Link”
To unlink a case, click the “Trash Bin” icon in the sidebar next to the test case you want to unlink (an icon will appear when you hover over the linked case):
2. Test runs
Switch on “Qase: Runs” module through the options:
In the module that appeared, click “Link a run”:
Use the search box to find the needed run by title, and click Link to attach it to the issue:
Linked run and the statuses of cases in it are now shown in the issue:
Any runs you have linked to Jira issues while setting up a run in Qase will also be shown in the “Qase: Runs” module.