To ensure only relevant, accurate and complete issues are provided by Applause to your team, all results submitted by the testers need to be triaged and eventually either approved or rejected.
As an Applause customer, you have the ability to view and triage issue reports in real time, as they are being submitted. However, we suggest starting triage when your TTL completes the initial triage to ensure all reports match with your expectations.
Triage Actions on an Issue Report
You can perform various actions on issue reports which we will review in this section.
Triage Actions You Can Perform on an Issue Report
- Approve or reject the issue
- Rate the issue's value when approving
- Message the tester, in case you require further information on the issue
- Leave notes to the TTL, TE and the TSM if needed
- Edit the issue if needed so it is on par with your content expectations
How to Triage an Issue Report
To perform triage actions on an issue report, click on the three dot menu while you are on the issue report details page.
Apply changes to the issue report details.
The export icon next to the pencil icon, allows you to export the issue report to CSV or to your BTS if it is configured for your product.
If BTS is configured for your product, issue reports can be marked as Manually Exported to BTS, if you’re going to export the issues manually to your BTS. This is explained in more detail in the Additional Actions on Issue Reports course.
Approve the issue as a valid one. You will be asked to set the issue value: Somewhat, Very or Exceptional.
Note: After an issue is approved, the “Approve, Reject, Request More Information” options will be grayed out and inaccessible.
Approve the issue for the sake of tester rating and payout, yet there is no intention to fix it.
Reject the reported issue as invalid. You will be asked to set the reason for rejection: Duplicate, Need More Info, Did Not Follow Instructions, the issue is Out of Scope, the scenario Works as Designed or any other reason. You are encouraged to add this issue to your Known Issues list to prevent future reporting of it.
The issue report is unclear and you’d like the tester to update it.