About the Bug Reports category

Bug reports

A bug is a demonstrable problem that is caused by the code in the platform. Good bug reports are extremely helpful - thank you!

Guidelines for bug reports:

  1. Use community search — check if the issue has already been reported.
  2. Check if the issue has been fixed — try to reproduce it using the latest version of the platform: sometimes you must deploy your application again to get changes.
  3. Isolate the problem — create a live example to demonstrate bug.

A good bug report shouldn’t leave others needing to chase you up for more information. Please try to be as detailed as possible in your report. What is your environment? What steps will reproduce the issue? What browser(s) and OS experience the problem? What would you expect to be the outcome? All these details will help people to fix any potential bugs.


Short and descriptive example bug report title

A summary of the issue and the browser/OS environment in which it occurs. If suitable, include the steps required to reproduce the bug.

  1. This is the first step
  2. This is the second step
  3. Further steps, etc.

Attached screenshots is very valuable to identify and resolve an issue - please properly label and annotate each screenshot.

<url> - a link to the application with a test case
Project ID - your project ID for our team to check
Deploy ID - if you think that your issue is region-specific

Any other information you want to share that is relevant to the issue being reported. This might include the lines of code that you have identified as causing the bug, and potential solutions (and your opinions on their merits).