Support is online. Detailed reports help us respond accurately.

BUG_REPORT_GUIDE

Turn “it broke” into a useful starting point.

You do not need to be technical. A short sequence, the result you expected, and the result you saw are often enough.

01

Start with the outcome

Write a short title that says what failed and where: “PDF export is blank after choosing landscape” is more useful than “Export broken”.

02

Describe the smallest repeatable sequence

  1. Begin from a known state, such as signing in or opening a specific page.
  2. List each click, selection, or command in order.
  3. Say whether the same steps fail every time or only occasionally.
03

Separate expected and actual results

“I expected a CSV download; instead the button showed a spinner indefinitely” makes the gap unambiguous.

04

Add safe context

A development version, browser, operating system, recent change, and exact error can narrow an investigation. Remove credentials, tokens, payment information, and private customer data first.

05

Use screenshots carefully

Capture the relevant area and redact sensitive information. Attachments remain protected behind administrator authorization or your private ticket token.

Ready to report it?

Every technical field is optional.

Start a bug report