How to report a bug effectively

The information we need to fix a website problem fast — how to describe what's wrong, what to include, and where to send it.

When something on your website isn't working right, the faster and more clearly you can describe it to us, the faster we can fix it. This guide explains what to include in a bug report and how to send it.

Quick summary

A great bug report includes: what you saw, what you expected to see, the URL of the page, a screenshot, and what you were doing when the problem occurred. The more detail you give us, the less time we spend guessing — and the faster we fix it.

Why good bug reports matter

We can't fix what we can't reproduce. Vague reports like "the website is broken" or "something looks wrong" force us to play detective before we can even start fixing.

A clear report with the right information means we can:

Understand exactly what's wrong
Reproduce it ourselves (see it happening)
Identify the cause
Fix it faster

What to include in your report

Use this checklist every time you report a problem:

Include	Why
The URL of the page	The web address in your browser bar. Paste it exactly.
What you see	Describe what looks wrong — in plain words.
What you expected to see	What should it look like or do?
A screenshot	A picture is often clearer than words.
What you were doing	Were you on a phone? Clicking a specific button? Submitting a form?
When it started	Did it just start? Has it been like this for a while?
Which browser/device	Chrome on a laptop? Safari on an iPhone?

How to take a screenshot

Press Command + Shift + 4. Your cursor turns into a crosshair. Click and drag to select the area you want to capture. By default, the screenshot saves to your desktop.

For a full-screen screenshot, press Command + Shift + 3.

How to write a clear description

Good example:

"On the Contact page (https://example.com/contact), when I submit the form with a valid email and message, the page refreshes but I don't receive the confirmation email. This started about three days ago. I'm using Chrome on a Windows laptop."

Not enough information:

"The contact form isn't working."

Both describe the same problem. The first one tells us exactly what to investigate. The second one could mean dozens of different things.

Where to send your report

Log a task in ClickUp. This is the best way — it keeps a record, lets you attach screenshots, and ensures nothing gets lost. See How to submit a new request.

Or email us. Send your report to support@chykalophia.com — unless your project lead has given you a different address. Attach your screenshot directly to the email.

For urgent issues. If the problem is causing immediate harm to your business (site down, checkout broken, security incident), see When & how to request emergency support.

What happens after you report

We acknowledge your report (faster for care plan clients)
We reproduce the problem on our end
We investigate the cause
We fix it and test the fix on staging where relevant
We let you know it's resolved and what caused it

No such thing as too much detail

It's impossible to give us too much information about a bug. More is always better. If you're unsure whether something is relevant, include it anyway.

Common questions

What if I can't reproduce the problem after taking the screenshot?

Share what you have anyway. Intermittent problems are real problems even if they don't happen every time. Tell us what you saw and that it was intermittent — that's useful information.

What if I don't know the URL?

Look at your browser's address bar — that long line at the top starting with https://. Copy and paste it into your report. If you were on a page but navigated away, use your browser history (usually Command+Y on Mac or Ctrl+H on Windows) to find it.

Is it a bug or a feature request?

A bug is something that's broken — it used to work or it should work but doesn't. A feature request is something new you'd like added. When in doubt, report it — we'll clarify if it falls into a different category.

Should I try to fix it myself first?

For content issues (typos, outdated info), yes — go ahead and fix those. For anything technical — layout problems, broken functionality, errors — please don't try to fix it yourself first. You might accidentally change something that makes it harder for us to diagnose the real cause.

Need a hand?

If you're stuck, email support@chykalophia.com and we'll help. Include your website address and a screenshot if you can.

How to report a bug effectively

On this page