A good bug report lets an engineer reproduce the fault on the first attempt. That is the whole goal. Everything below serves it.
Write reproduction steps
Number them and start from a clean state. For example: 1. Open the products page in a private window. 2. Add any item to cart. 3. Click checkout. 4. Enter a Malaysian phone number in the phone field. 5. Click Place Order. 6. The page reloads with an empty cart and no error message.
Anyone should be able to follow those steps without asking you a question. That is the test of a good report.
Separate symptom from diagnosis
Tell us what you saw. If you also have a theory about the cause, add it at the end and label it as a guess. Reports that lead with a diagnosis can send an engineer down the wrong path for an hour.
Include the boring details
- Browser and version, operating system, device.
- Whether you were logged in, and with what role.
- The exact data you entered. Bugs often depend on the input, such as an apostrophe in a name or a long address.
- Whether it happens every time or one time in five.
Capture evidence
Screenshots must include the full window with the address bar visible. For anything interactive, a short screen recording is worth ten screenshots. If you are comfortable doing it, open the browser developer console with F12, reproduce the fault, and screenshot any red error lines. That single step often identifies the cause immediately.
One bug per ticket
Bundling five faults into one ticket means none of them can be closed until all five are done, and the thread becomes impossible to follow. Raise them separately in the portal at crm.zylax.com.my and reference each other if they are related.
If it is intermittent
Note the exact times it occurred. Server logs are timestamped, so times let us find the matching entries.
Send what you have and reply to your email thread or contact [email protected] if you need help capturing any of this.
