Product Feature

UI Bug Tracking for Product Teams

Detect UI bugs, collect client comments, and track both to fixed with labels and assignees, in OverlayQA or with two-way sync to your tracker.

UI bug tracking is the practice of logging visual and interface defects with the evidence a developer needs, then following each one from report to fix. In OverlayQA, detected bugs and client comments land in one issue list with labels, assignees, and comment threads, and can sync two-way with Jira, Linear, Notion, Asana, or Trello.

Why UI bugs and client feedback get lost

• Bug Reports in Five Places: UI bugs arrive in chat threads, email, screenshots, and spreadsheets, and nobody can tell which ones are still open. Fixed bugs get reported twice and open ones get lost.
• Bugs Without Context: A screenshot with an arrow does not tell a developer which element, which viewport, or which CSS value is wrong. The fix starts with reproducing the bug.
• No Clear Owner: When a bug has no assignee, everyone assumes someone else picked it up. Bugs sit open until a client finds them again.
• Client Feedback Stuck in Email: Clients send notes by email or in a shared doc, and someone has to retype each one into the tracker. Client requests slip between the inbox and the backlog.
• Two Tools, Two Statuses: A bug is closed in the developer tracker but still open where it was reported, so design and QA re-check work that already shipped. Nobody trusts either list.
• Only the Bugs Someone Noticed: A tracker only holds what a person spotted and wrote down. Accessibility failures and design drift that nobody saw never get a ticket. The backlog looks clean while the page ships with bugs.

How OverlayQA tracks UI bugs to fixed

Detect and Capture Bugs With Full Context

Click any element to capture a screenshot, CSS selector, computed CSS, and viewport. Accessibility audits, Auto Review, Design Tokens, Visual Comparison, AI Visual Comparison, and scheduled scans add the bugs nobody spotted, each as its own tracked issue. Every issue starts with the evidence a developer needs.

Labels, Assignees, and an Active Issues View

Every issue gets a readable ID like OQ-127. Add custom labels, assign an owner, and open the Active issues view to see only open work. Filter by label or creator, search the Issues page, and update status, type, or severity on many issues at once. Everyone can see what is open and who owns it.

Team Comments and Client Feedback in One Place

Every issue has a comment thread with @mentions, real-time notifications, files, and emoji. Each comment is Team only or Team and clients. Clients comment through a review link with no account, and each comment becomes a tracked issue automatically. Client feedback lands where the team already works.

Track in OverlayQA or Sync Two-Way

Run the whole loop inside OverlayQA with no tracker, or sync two-way with Jira, Linear, Notion, Asana, and Trello so status, assignee, and comments stay in step. AI coding agents read and update the same issues through the OverlayQA MCP server. One status, wherever your team works.

Frequently asked questions about UI bug tracking

What is UI bug tracking?

UI bug tracking is logging visual and interface defects with the evidence a developer needs, then following each one from report to fix. OverlayQA keeps captured bugs, detected bugs, and client comments in one issue list with labels, assignees, and status.

Do I need Jira or Linear to track issues in OverlayQA?

No. Teams can run the whole loop inside OverlayQA: capture or detect an issue, label it, assign it, discuss it in comments, and mark it fixed, with no export. Connect a tracker only if your developers already work in one.

What syncs back from my issue tracker?

Status, assignee, and comments sync back from Jira, Linear, Notion, Asana, and Trello. Priority also syncs back from Jira and Linear. Slack posts when an issue is created, assigned, or commented on, and supports the /overlayqa resolve and reopen commands.

Can clients leave feedback without an account?

Yes. Send a client review link and clients comment on the page with no account. Each comment becomes a tracked issue in your project, and clients can attach files and reply in the thread. The page can carry your logo and colors on every plan.

Who can see a comment on an issue?

Each comment has an audience. Team only is the default and keeps the comment inside your team. Team and clients shows it to clients on the review link. Files attached to a comment follow the same audience.

What files can I attach to a comment?

PNG, JPG, and PDF files, up to 10 files and 10 MB per comment. Choose Add files in the comment box, and use Add emoji to insert an emoji.

How do labels work?

Create one with New label…, and owners and admins look after the full list in Manage labels. Filter the Issues page by label, including No labels to find untagged work. Labels also appear on exports and shared reports.

Can AI coding agents work from these issues?

Yes. AI coding agents such as Claude Code and Cursor connect through the OverlayQA MCP server (@overlayqa/mcp) to read issues, add comments, apply labels, and move issues, so an agent can pick up a bug and update it when the fix is done.

How many people can use it?

Freelancer includes 1 seat, Starter 5, and Pro 20. Every plan includes all integrations and starts with a 14-day free trial.