Report Classification

When there’s a new QA or Client Testing task/report assigned to the dev, PM must classify through the “Report Type” custom field as shown below.

Definitions

BLOCKER: Means you are blocked to move forward (for example you can’t log in, or clicking on a button doesn’t do anything)

BUG: It’s an issue with the platform (Bubble, Glide, FF, WF). Reference Platforms Best Practices

Fix: Something needs fixing.

User Error: User who submitted the report thought there was an error, but actually they don’t understand how to use the app, so the error is on them.

Different from Wireframe: It is on the wireframe, but it is not on the app.

UI/UX Enhancement: UI/UX needs improvement (when this is submitted during Client Testing, it is subject to be an add-on).

Copy Change: Text in the app needs changing.

Missing on Wireframe: Request should’ve been on the wireframe in the first place.


⚠️ This classification will affect the KPIs for devs and designers.

 


Was this article helpful?
© 2025 LowCode Internal Docs