How to Format a Proper Bug Report

Sort:

jdcannon

Aug 10, 2017

Beta Team!

Making sure that our dev team has all the correct information can dramatically lessen the amount of time required to fix bugs. To that end, please use the following template when submitting bug reports to Jira/Usersnap.

Bug Report Form:

Overview: Give a brief overview of the bug or suggestion.

Environment: List relevant browser, operation system, app version, device type, etc. Also add relevant username/profile links, game links, tournament ids etc.

Steps to Reproduce: Give very specific step by step instructions for recreating bug even if the steps seem stupid. Include screenshots or video to insure there is no ambiguity.

For example, don't say, "Step 1. Sent 1 minute challenge" instead say, "Issue 1 minute challenge from post game modal after having finished another game."

Result: Give detailed explanation of what happens as a result of the steps you listed above. Provide screenshot or video to demonstrate bug exactly.

Expected Result: Provide what should have happened instead of the bug, even if it seems obvious.

Use the template below. Simply Copy Paste it in the bug report pop up:

Beta Bug Report

Overview:

Environment:

Steps to Reproduce:

Result:

Expected Result:

Chess.com always happy to recieve feedback, especially when you encounter bugs or when features don't work as well as you expect. Though, we do ask that you keep your feedback respectful both in bug reports and public forums. Abusive behavior may result in removal from Beta club.

Thank you very much! Your feedback will help greatly!

This forum topic has been locked