Working with Applause boosts your product testing with speed, coverage and scale with unparalleled access to a global curated community of available, professional testers and virtually any device configuration out there. Assisted by your Applause team, you will be able to test faster, complete more test runs – whether structured or unstructured, manual or automated, functional or other – and improve the quality of issues you track and ultimately fix.
At the same time, the Applause platform is not meant to replace your Bug Tracking System (BTS). Systems like Jira, Linear, Azure DevOps (TFS), monday.com and others can still be utilized by your team to keep track of reported issues, the assignment to engineer, sprint, release etc., as well as fix status, time and effort, and related communication. BTSes are a major efficiency gain when implemented properly, and countless teams rely on them to manage their day-to-day tasks.
A key prerequisite for such efficiency gains is the accurate creation and update of issues (or ‘bugs’, ‘defects’, or ‘tickets’) with all required data and in a timely manner. A manual process for transferring the issues reported in the Applause platform often proves to be challenging for Engineering teams striving to meet such criteria at scale. This is precisely where integrating the Applause Platform with your BTS comes into play.
For each Applause bug, a new issue will be created in your BTS. Its identifier will be available from the Applause platform for convenient look-up.
Additionally, the two-way integration (available for Jira and ADO) allows updates from your BTS to flow into the Applause platform on the issue prioritization and fix status. This means more accurate in-platform reporting, including your Applause Quality Score as well as workflows such as Bug Fix Verification. Learn more about the Applause Quality Score here.
Note the following prerequisites and limitations before integrating your BTS with the Applause platform.
The Applause platform must be able to communicate with your BTS. Contact your IT resources to ensure this prior to configuring the integration.
Note: This step is only required for an on-premise deployment. If you are connecting with a cloud system, this configuration is not needed.
You should configure your firewall or security settings to permit the following IPs for the Applause platform to access your BTS remotely:
The BTS-Specific Integration implements an API published by the 3rd party responsible for the BTS. These integrations tend to be tighter. At the same time, there is clearly a finite list of BTSs we can support. If your specific BTS is not included in the list of supported systems, you may need to use the Generic integration.
As in most integration products, the BTS-Specific Integrations implements a set of APIs published by 3rd parties. Thus, functionality is dependent on 3rd party offered options and as such the integration functionality may slightly differ.
The integration sends data to an email inbox or a webhook.
For integrations where authentication is enabled, only Basic auth is supported at this time. Methods like two-step authentication and OAuth are currently not supported.
Applause platform integrates with a variety of BTS Connectors. We currently support the following connectors:
With any connection you enable, be sure to thoroughly validate your integration to make sure All Fields and Values are properly matched. Example: Applause may identify Severity level 1 as Low, whereas your company may use level 1 as Critical.