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

Overview

Available features

Launching tests from Jira

Other features

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.