QA Service for JIRA
by
test IO's Jira Add-On "QA Service for Jira" enables you to review and export bugs that get reported by our network of professional testers, so you can ship faster and sleep better.
Recent Releases
User Stories in your Jira Add-On
You can now see results across tests and per user story directly in Jira 🎉
Bug Fix Confirmation
Request Bug Fix Confirmations for your own bugs from Jira to 🎉
Overview
Available features
Jira Cloud Add-On
Latest changes
User Stories
See results of tests containing User Stories
Launching tests directly from Jira 🚀
Features
Default field mapping
Customizable field mapping
Known Bug Status sync
Two-way Comments Sync between Jira to test IO
test IO Bugs in Jira
Configure a Project
Jira Add-On ↔ test IO Interface
Re-Export a Bug
Bug Triage in test IO interface AND Jira Add-On
Bug Fix Confirmation via Jira
For test IO Bugs
For your own Bugs
Jira Server Add-On
Version 2.7.0 and higher
User Stories
You can now see the results of tests that include User Stories
Checking results across multiple tests? Not a problem! You can display the results per test or per user story.
Support for Jira Server 8.20.x (8.21. is being tested)
Version 2.3.0 - 2.6.6
Launching tests directly from Jira 🚀
Bug Fix Confirmation
Tickets in Jira that have received a positive Bug Fix Confirmation get automatically closed now (Jira Issue Workflow).
Button “Confirm Fix” is not displayed in all JIRA projects anymore.
Support for Jira Server Versions:
Please visit the version history for more details.
Previous Jira Server Versions
Version 2.1.4
Redesigned Settings pages
Improved user selection
Improved attachment upload
User scope to project in mapping selection
Tested for compatibility with Jira Server 8.13.x
Version 2.0.x
New UI for bug triage
Added labels to be used for the issue & severity mapping
Bug Fix Confirmation for your own Bugs via Jira
Version 1.8.x; 1.9.x
Added overview of recurring background jobs
Version 1.6.x; 1.7.x
Added: Bug Fix Confirmation for test IO Bugs
Added: Jira Add-On ↔ test IO Interface
Added: Re-Export a Bug
Added: Bug Triage in test IO interface AND Jira Add-On
Tested for compatibility with Jira Server 7.5.x - 8.x
Version 1.5.x
Added: test IO Bugs in Jira
Added: bug triage in Jira
Tested for compatibility with Jira Server 7.5.x - 8.5.4
Version 1.3.x
Default field mapping
Known bug status sync
Comments sync from test IO to Jira
Tested for compatibility with Jira Server 7.x - 8.5.4
Results at your fingertips
User Story results are now accessible directly in Jira
Here is to access your User Story results
Go to the results under the test IO menu entry and navigate to the tab "User Stories".
Automatically available for Jira Cloud & Jira Server 2.7.x and higher
(pricing plan limitations apply,
please contact your account manager if the option is not displayed in Jira or for further information)
Fix bugs faster for everyone.
Bug Fix Confirmation is now available for test IO and your own bugs
Here is how we make it work
Step 1) A bug was fixed by your development team
Step 2) Anyone with access to the bug ticket in Jira can now request a bug fix confirmation via test IO
Step 3) It takes about 30 minutes to get a result from an experienced crowd tester.
Step 4) Depending on the result, you can request additional confirmations or deploy your bug fix right away.
Automatically available for Jira Cloud & Jira Server 2.0.x and higher
(pricing plan limitations apply,
please contact your account manager if the option is not displayed in Jira or for further information)
Go to your Jira actions
Navigate to the Jira actions and click on
"Confirm fix via test IO"
Submit your request
You can customize your request or simply select the default to save even more time.
Receive results in Jira
We will sync the result as a comment with the most important information and deep links to the test IO platform (a user account is required).
Launching tests from Jira
(Jira Cloud & Jira Server 2.3.x and higher)You can access this feature from the same place where you are able to triage Bugs. You have a new tab to get to the Test Cycle creation.
Creating a test cycle will utilize a Test Template. You can create templates of your Tests in the test IO platform, which you can use to easily configure an Exploratory Test in the Plugin.
Note: In order to use this feature, you have to create Templates. There are no default ones, as it's a customary item for all of our Customers. Template creation can be done only in the test IO platform. Saving a Test as a Template there, enables you to choose it later in the Plugin.
Configuring the Test
(Jira Cloud Add-on only)
Configuring the Test from the plugin is easy: just select your Product and Section, choose the desired Template, fill the Test related fields and you are good to go.
Other features
Configure a Project
(Jira Cloud Add-On only)It's clear now which Jira projects have a configured bug export.
On the left you find the list of configured Jira projects.
With a click on "Configure Project" in the top right, a new configuration can be added.
Jira Add-On ↔ test IO Interface
When a new configuration is added in the Jira Add-On, it will automatically be created in your account. That enables you and us see and use it like any other connection that was created in the test IO interface originally.
When a connection is deleted here, it will also be deleted in the Jira Add-On.
Re-Export a Bug
Connections that were create from the Jira Add-On are available in Jira and test IO now, that allows you to re-export a bug from the test IO interface.
That is sometimes necessary and is now possible easily from within the test IO interface.
Bug Triage Everywhere
Connections that were create from the Jira Add-On are available in test IO now, it is possible to do the bug triage accept, reject, request information, change severity from within both interfaces therefore, in Jira directly as well as test IO.
When bugs are exported from test IO, they will be exported using the connection created in the Jira Add-On.
Default Field Mapping
You can map required and optional Jira fields to predefined fields like bug title and description.
Custom Field Mapping
You can customize the exported information that you receive from test IO for any Jira field.
test IO Bugs Page
The Add-On will automatically add a test IO bugs page in your Jira projects.
That way you have easy access to test IO bugs.
Bug Triage
Interact with bugs from your test IO tests directly in your Jira, you don't have to switch tools.
Known Bug Status Sync
You want to automate?
Sure! When a bug is fixed, configure the status that should trigger the known bug status to be removed on the test IO bug.
Bug Comments Sync
If you want to make sure no information is lost, you can configure a comment sync that is triggered with a defined string like "@testio". You don't need to add a user for that.
Maintenance Tab
(Jira Server Add-on only)
Having issues? Before starting to panic, you can check if the testIO plugin is operational. This can also help us tremendously to troubleshoot your problems.
Run a sample request towards our API, to see if your Jira instance is capable of reaching our backend while simultaneously checking if your database is a supported one and if the plugin is capable of communicating with it.
If anything goes sideways, you can download the application logs which will aid our engineering team in solving your issue.
How to install and configure your Jira Add-On
Do I need to be a test IO customer to use this Add-On?
Yes.
With this app and as a test IO customer you can connect test IO to your Jira instance in minutes, so testers’ reports are available without leaving Jira. If you’re not a test IO customer, this app will install, but it can't be used without a test IO subscription. We’re happy to give you a free test for one of your current projects so you’ll know what our testers can do and how it fits with your Jira workflow.
API Token
To install the app in your JIRA instance, please follow the installation guide found in the Atlassian Marketplace listing.
After you've successfully installed your app, open the test IO platform in a new tab and log in to your customer account.
Click on "Integrations" in the top left navigation, navigate to the API details.
You should now see the API token for your user.
Copy the API token.
Configuration for Jira Cloud & Jira Server 1.6.x and higher
Switch back to your JIRA software and navigate to the "Apps" tab, found in the administration section.
In the left navigation bar you should see the "Configuration" controls for the test IO App.
Click on "Configuration".
Navigate to the "Token" tab. Paste the API token from your test IO customer account and click on "Save".
Navigate to the "Projects" tab and select which JIRA projects should be mapped to the respective test IO products. You can map multiple test IO products to one JIRA project.
Select the JIRA issue type to be synchronized with test IO bugs.
Under "Mapping", configure how test IO fields are mapped to JIRA. Required JIRA fields are marked with an asterix ( * ).
Enter a "Comment Sync" string. This string will be used as a tag for comments to be synchronized with the test IO platform. The default string is "@testio".
Select which workflow status represents "fixed" in your JIRA project. This will sync the status back to test IO and mark known bugs as fixed.
You're all set! New test IO bugs and comments will be synchronized automatically! In the test IO Bugs page, you can accept and reject the issue to get them exported into your Jira project.
You can now work in both interfaces to accept, reject and export bugs. 🎉
You can re-export bugs if necessary via the test IO interface.
Configuration for Jira Server 1.5.x
Switch back to your JIRA software and navigate to the "Apps" tab, found in the administration section.
In the left navigation bar you should see the "Configuration" controls for the test IO App.
Click on "Configuration".
Navigate to the "Token" tab. Paste the API token from your test IO customer account and click on "Save".
Navigate to the "Projects" tab and select which JIRA projects should be mapped to the respective test IO products. You can map multiple test IO products to one JIRA project.
Select the JIRA issue type to be synchronized with test IO bugs.
Under "Mapping", configure how test IO fields are mapped to JIRA. Required JIRA fields are marked with an asterix ( * ).
Enter a "Comment Sync" string. This string will be used as a tag for comments to be synchronized with the test IO platform. The default string is "@testio".
Select which workflow status represents "fixed" in your JIRA project. This will sync the status back to test IO and mark known bugs as fixed.
You're all set! New test IO bugs and comments will be synchronized automatically! In the test IO Bugs page, you can accept and reject the issue to get them exported into your Jira project.
⚠️ Important: If you had an older Jira Server Add-On version installed, you or your team might be used to accept and reject bugs in the test IO interface. This new version will only work correctly if you perform those actions within the Jira test IO bugs page. We are working on the support of both ways.
Configuration for Jira Server 1.4.0
We decided to skip that version :)
Configuration for Jira Server 1.3.0 or lower
Switch back to your JIRA software and navigate to the "Apps" tab, found in the administration section.
In the left navigation bar you should see the "Configuration" controls for the test IO App.
Click on "Configuration".
Navigate to the "Token" tab. Paste the API token from your test IO customer account and click on "Save".
Select a "Reporter", that will be the JIRA user to create test IO issues and click "Save". (Note, that this user needs to have the permission to create issues!)
Navigate to the "Projects" tab and select which JIRA projects should be mapped to the respective test IO products. You can map multiple test IO products to one JIRA project.
Select the JIRA issue type to be sychronized with test IO bugs.
Under "Mapping", configure how test IO fields are mapped to JIRA. Required JIRA fields are marked with an asterix ( * ).
Enter a "Comment Sync" string. This string will be used as a tag for comments to be synchronized with the test IO platform. The default string is "@testio".
Select which workflow status represents "fixed" in your JIRA project. This will sync the status back to test IO and mark known bugs as fixed.
You're all set!
⚠️Bugs that are accepted in your test IO interface and are not yet exported will be exported to your JIRA instance in one go.
From now on, bugs that get accepted will be synced every 5 minutes, status changes and issue comments will be synchronized automatically according to your settings.