Issue Types

During User Acceptance Testing (UAT), every piece of feedback you submit is sorted into one of three issue types: a bug, an enhancement, or a discussion. You’ll choose the type right in the Marker.io report form.
Picking the right type matters because each one is handled differently. It helps us understand what you’re really asking for, route it to the right person, and prioritize it against your launch. The good news is the three types are easy to tell apart — and if you’re ever unsure, you can always submit it as a discussion and we’ll help sort it out.

Bugs

A bug is a functional issue — something is broken or not working the way it was meant to.

A bug can be major, like a user role not having the access it was supposed to, or search not returning the results it should. It can also be minor, like a layout that breaks only on an older browser.

Examples:

• A button or link doesn’t do anything when clicked.
• A form won’t submit, or submits incorrectly.
• A page displays broken layout or missing content.

Anything that blocks a core task or seriously disrupts the experience should be reported as a bug and given an appropriate priority. If a lot of bugs come up at once, we’ll tackle the highest-priority ones first and may schedule lower-priority items for later so we can protect your timeline.

Enhancements

An enhancement is a suggested improvement — something that wasn’t part of the original plan but that you think would make the experience better.

This often happens during testing: a feature works exactly as designed, but once you see it in action you spot a way it could work even better. That’s valuable feedback, and we want it.

A couple of things to know:

• Enhancements are weighed against your timeline and budget. Many are a great fit for a future update after launch.
• If an enhancement is substantial enough to change the original scope, we may treat it as a new feature and plan it as its own piece of work.

To keep your launch on track, “nice to have” enhancements are usually documented for a future iteration rather than squeezed in before go-live.

Discussions

A discussion is a question or a request to talk something through. Since UAT is often your first hands-on time with the new site, questions are completely natural — and welcome.

Use a discussion when you’re not sure how something is meant to work, when you want clarification, or when you’d like to think through an idea together before deciding whether it’s a bug or an enhancement.

We genuinely like getting these. A question usually means you’re digging in, and answering it quickly keeps your testing moving. Many discussions also turn into a quick “here’s how that works” answer — which is exactly what UAT is for.

Before you report

Not sure which type something is? Ask yourself:

• Is it actually broken, or just not what I expected? If it works but you’d prefer it behaved differently, that’s usually an enhancement, not a bug.
• Am I sure how it’s supposed to work? If you’re not certain, a discussion is the perfect choice — no need to guess.
• Is this new, or was it part of the original plan? Something new is an enhancement; something that was promised and isn’t working is a bug.

It’s very common for something that feels like a bug to turn out to be a feature working as intended, a setting you haven’t found yet, or a quick how-to. When that happens, it’s not a wasted report — it’s a chance for us to show you how the new site works, which is part of what UAT is all about. So when in doubt, submit it. We’ll always help you figure out what it really is.

---

Related: Priority Levels · How to report an issue