Exporting Bugs and Feedback and Crashes to Jira and other Bug Tracking Systems

Exporting Bug, Feedback and Crash items to Jira and other BTS’s is possible through the web panel.

As well as the bug, feedback or crash data you’ll also export screenshots and session data.

Step 1: Set up the BTS Integration via the right menu item ‘Integrations


Step 2: Select which BTS you wish to integrate with :




In JIRA you must enter the host url, JIRA username, password, Issue Type and Project Key.

URL: the url where you JIRA is hosted. Please note that this has to be accessible to MBM and not blocked by a firewall. See here for more details about firewalls.

Username: this is usually not an email address but the first part of an email address before the ‘@’ sign. Please consult your JIRA admin if you don’t know your username.

Issue Type: is the default issue type in JIRA that you want creating after the export. E.g. in the above example all crashes, bugs and feedback will be reported as a ‘Bug’ once exported.

Project Key: Is the project identifier in JIRA

Once you click ‘Update Integration‘ you will be asked to define some BTS field mappings for mandatory components.

Step 3: Define mappings


The mappings will differ for each JIRA project depending on how you have configured your project.

Clicking ‘Save’ will confirm the mappings and the BTS export is in place.

Step 4 Exporting Issues  

You can export Bugs, Feedback or Crashes either from the Dashboard, Reports or the details section.

integrations3 integrations4









You can either export issues individually or via a bulk export.

Once reported a link will be provided to the issue created in the BTS.


Tagging Issues

It’s now possible to add tags to your bugs and feedback. Tagging helps you keep track of important issues and organise them in a way that makes sense for your project.

Please Note: This feature is currently only available to Admin users.

You can add / edit tags from either the list view.


Or from the details view.

You can then search for the tags.


DMARC Policy and Email sender restrictions

For a full explanation of DMARC you can read about it here. But in a nutshell DMARC is a mechanism aimed at preventing spammers and email fraudsters from spoofing email addresses to spam or phish.  

If your mail server prevents spoofing your domain in the sender field of email sent from MBM then emails must be sent from the applause server.


Reach out to Participants with chat

MBM now allows you to reach out to participants  via a simple chat window.

Every bug or feedback details page now has a dedicated chat.

You can start the conversation by clicking the blue button (this will activate the chat for that bug/feedback)

A text area with a hint “Type message here…” will appear and this is where you should enter the message and click “Send”.


You will see your message appear the participant will also be notified of each message via email. (in the example above they’ll receive 2 messages)

The participant will receive a branded (assuming you’ve added branding) email with a link to a chat.

This can be opened via a mobile phone or desktop and will take them to a chat with details about the bug of feedback they created plus the chat history.

The participant can reply to your messages via a unique chat room related to the bug or feedback.

Chats will auto-update periodically.

Closing a conversation

At the bottom of the chat window there is a link to close a conversation. Closing the conversation will disable this particular chat. Chats can be reopened at any time by the beta manager.

Showing users how to use the Applause SDK: In app tutorial

The mobile SDKs are fairly simple for end users – they shake and can then report bugs or give feedback. However, we’ve also added an optional in app tutorial to inform users how to use the SDK.



If you don’t want to present this tutorial to your participants / testers then it can be disabled via the web panel on your app settings.