Integration

monday.com Integration for Design QA

Export UI bug reports from any live page into monday.com items with the screenshot, CSS selector, computed values and viewport data a developer needs. Each item lands on the board and in the group you pick, and status and priority sync both ways.

Items that arrive ready to work

monday.com teams plan work on boards, and a visual bug is only useful if it lands on the right board with enough detail to fix. OverlayQA's monday.com integration creates an item in the group you choose, named after the issue. monday.com items have no description field, so the item's first update holds the issue description: the page URL, the element's selector, its computed CSS values, and the browser and viewport it was seen in, with the screenshots and files attached to that update. The issue's severity fills the board's Priority column when a label matches.

Issues can come from a click on the live page, from a client comment on a review link, or from a workflow that found them: Auto Review, the accessibility audit and the design-token checks all produce issues with the same structure. Export one issue from its actions menu or up to 100 at once with bulk actions, on the dashboard or in Team Review.

After export the item and the issue stay in step. Change the item's status to a label such as Working on it or Done, or its Priority to Critical, High, Medium or Low, and the OverlayQA issue follows; archive or delete the item and the issue closes. Change the title, status or severity in OverlayQA and the item follows, using the labels your board already has. Updates written on the item appear on the issue with their author's name. Assignees do not sync.

How the monday.com integration supports product teams

• Full context in every item: selector, computed CSS values, browser, viewport and screenshots travel with the issue in the item's first update.
• Routed to the right group: pick the board and the group at export, so frontend issues land where the frontend team works.
• Status and priority sync both ways: the item and the issue follow each other, and updates on the item come back to the issue.
• Found and captured issues alike: issues from Auto Review, the accessibility audit and design-token checks export with the same structure as a captured bug.

Frequently Asked Questions

How do I export issues from OverlayQA to monday.com?

Connect monday.com from the Integrations page in the OverlayQA dashboard; the first connection from a monday.com account needs an account admin, because monday.com lets only admins install apps. Then open any issue, choose Export to monday.com, pick the board and the group, and confirm. Bulk actions export up to 100 issues at once, on the dashboard or in Team Review.

Does monday.com sync back to OverlayQA?

Yes. Changing an exported item's status to a label such as Working on it or Done, or its Priority label to Critical, High, Medium or Low, updates the OverlayQA issue, and archiving or deleting the item closes it. An update someone writes on the item appears on the OverlayQA issue with their name. Changes to the title, status or severity in OverlayQA update the item, using only labels the board already has. Assignees do not sync with monday.com.

What does a monday.com item from OverlayQA include?

The item is named after the issue. monday.com items have no description field, so the item's first update holds the issue description with its screenshots and files attached to that update, and the issue's severity fills the board's Priority column when a label matches.