Lorixen.
EN

Reporting a Bug to Your Developer So It Gets Fixed Fast

Short answer: A bug report gets fixed fast when the developer can make the problem happen on their own screen. That needs five things: the exact steps you took, what you expected, what actually happened, where it happened (page, device, browser, account), and a screenshot or short screen recording. Send one problem per report, say how urgent it is, and you'll usually skip the back-and-forth that turns a ten-minute fix into a week.

"The booking form is broken" is the most common bug report a developer receives, and it's almost impossible to act on. Broken for whom? On which page? Doing what? The developer opens the form, it works for them, and the ticket stalls. The template below fixes that.

The template

Copy this into an email, a shared document or your project tool. Fill in every line, even if the answer is "not sure".

Title: one line that describes the problem, not the feeling. Good: "Checkout button does nothing after adding a discount code." Not useful: "Website broken!!"

Where: the full web address of the page (copy it from the address bar) or the app screen name.

When: date and time it happened, as precisely as you can. "Today around 2:40pm" lets the developer find the matching entry in server logs.

Who: the account or email you were logged in as, and its role (admin, staff, customer). Never send passwords; the developer doesn't need yours.

Device and browser: for example "iPhone, Safari" or "Windows laptop, Chrome". If you know the versions, add them. If not, a screenshot of the browser's "About" page is enough.

Steps to reproduce:

  1. Go to the shop page.
  2. Add the blue linen apron to the cart.
  3. Enter the code AUTUMN10.
  4. Click "Checkout".

Expected result: "The checkout page opens with 10% off."

Actual result: "The button greys out briefly, then nothing happens. No error message."

How often: every time, sometimes, or once. If sometimes, mention anything that seemed different.

Severity: pick one (see below).

Attachments: screenshot, screen recording, any error message text copied exactly.

Severity: be honest, not loud

Agree these levels with your developer once, then use them consistently:

Level Meaning Example
Critical Customers can't buy, book or log in; data is wrong or exposed Checkout fails for everyone
High An important feature fails for some users, with no workaround Booking form fails on iPhones
Medium Something's wrong but there's a workaround Filter shows wrong count; search still works
Low Cosmetic or minor Button misaligned on one page

Marking everything critical means nothing is. If you're not sure, say so and describe the business impact in a sentence: "We've had three phone calls from customers who couldn't pay."

Capturing what you see

A 20-second screen recording often replaces a page of explanation, because it shows the exact clicks, timing and on-screen messages.

  • Mac: Apple's support pages describe pressing Shift-Command-5 to open the Screenshot toolbar, which can record the entire screen or a selected portion.
  • iPhone and iPad: start a recording from Control Centre using the Record button; Apple notes you may need to add it to Control Centre first.
  • Windows: Microsoft's Snipping Tool can capture a "video snip". Microsoft lists Windows logo key + Shift + R as the shortcut, then you select an area and press Start.
  • Android: many phones include a screen recorder in the quick settings panel; the name and location vary by manufacturer.

Tips: record the whole sequence from the start of the steps, keep it short, and don't show other customers' personal details on screen. Crop or blur if needed.

Bonus: copy the error from the browser console

If the problem is on a website and you're comfortable with one extra step, the browser console often shows the technical error behind a button that "does nothing". Chrome's documentation describes the Console as the place where developers view logged messages and errors. Open it (in Chrome, through the DevTools panel), repeat the steps, and screenshot any red error lines. You don't need to understand them; the developer will.

One problem per report

When three issues sit in one email, the easy two get fixed, the hard one gets forgotten, and the thread becomes unreadable. Separate reports can be prioritised, assigned and closed individually.

If you're collecting problems after a launch, a simple shared list works: one row per issue, with the template fields as columns. Many project tools support this too. GitHub, for example, lets repository owners set up issue templates so everyone filling in a report is prompted for the same information.

What happens after you send it

A reasonable process, which you can agree with your developer in advance:

  1. Acknowledgement: the developer confirms they've received it and asks any missing questions.
  2. Reproduction: they try to make it happen. If they can't, they'll ask for more detail. This is where good reports save days.
  3. Fix and test: the fix goes to a test version (staging) first where possible.
  4. Your check: you repeat your original steps on the test or live site and confirm it's fixed.
  5. Close: the report is marked done, with a note of what changed.

Ask for a rough timeframe per severity level, and agree how critical issues outside office hours are reported, especially for shops and booking sites that take orders at weekends.

Common reasons reports stall

  • No steps: "it just doesn't work".
  • Steps that skip the important part ("I logged in with a different account first" mentioned three emails later).
  • Screenshots cropped so tightly the page address and error are missing.
  • Problems reported days later with no date or time.
  • Several people reporting the same issue separately, in different words. Nominate one person to collect and send reports.

FAQ

What if I can't make the bug happen again?

Report it anyway, mark it "happened once", and include the time and what you were doing. Intermittent bugs often show a pattern once several reports exist.

Should I fix small text mistakes myself?

If you can edit content in your site's admin, yes. Report only things you can't change yourself, or ask your developer to show you how.

Is it okay to report a bug by phone?

For something critical, call, then follow up in writing with the template so nothing gets lost.

How much detail is too much?

Rarely an issue. Extra context is easy to skim; missing context costs a round trip.

Want a simple reporting routine set up for your site or app, with a clear path from report to fix? Tell us how you handle issues today.

Sources

WhatsAppLet’s talk