Integration

Basecamp Integration for Design QA

Export UI bug reports from any live page into Basecamp to-dos with the screenshot, CSS selector, computed values and viewport data a developer needs. Each to-do lands in the project and to-do list you pick, with a link back to the issue in OverlayQA, and completing, reopening or archiving the to-do, and its comments, sync back to the issue.

To-dos that arrive ready to work

Basecamp teams plan work in projects and to-do lists, and a visual bug is only useful if it lands in the right list with enough detail to fix. OverlayQA's Basecamp integration creates a Basecamp to-do in the list you choose, named after the issue. Inside the to-do are the page URL, the element's selector, its computed CSS values, the severity, and the browser and viewport it was seen in. Screenshots and the files attached to comments are uploaded to Basecamp and shown inside the to-do.

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, so a contrast failure and a misaligned button export the same way. Export one issue from its actions menu or up to 100 at once with bulk actions, on the dashboard or in Team Review.

One 37signals login can reach several Basecamp accounts. OverlayQA lists the projects from all of them, and when the login reaches more than one account, each project is shown with its account name. There is no field picker, so assignees and due dates are set in Basecamp after export.

How the Basecamp integration supports product teams

• Full context in every to-do: selector, computed CSS values, severity, browser, viewport and screenshots travel with the issue, so nobody reopens DevTools to rediscover the bug.
• Routed to the right list: pick the project and the to-do list at export, so frontend issues land where the frontend team works.
• 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.
• Status and comments come back: complete a to-do and the issue reads Resolved, reopen it and it is Open, trash or archive it and it closes; comments on the to-do appear on the issue.
• A way back to the source: every to-do ends with an Open in OverlayQA link to the issue, its comments and its screenshots.

Frequently Asked Questions

Which website feedback tools integrate with Basecamp?

Several website feedback tools send reports to Basecamp: Marker.io, Usersnap and Userback all offer Basecamp integrations, and OverlayQA does too. The difference is what gets filed. Those integrations send what a person reported. OverlayQA also finds issues nobody reported, through Auto Review, an accessibility audit and design-token checks, and files them to Basecamp with the same selector, CSS values and screenshot as a captured bug.

How do I export issues from OverlayQA to Basecamp?

Connect Basecamp from the Integrations page in the OverlayQA dashboard and sign in with the 37signals login that owns your projects. Then open any issue, choose Export to Basecamp, pick the project and the to-do list, and confirm. Bulk actions export up to 100 issues at once, on the dashboard or in Team Review. Each issue becomes a to-do named after the issue, with the page URL, element selector, computed CSS values, severity and browser details, and the screenshots shown inside the to-do.

Does Basecamp sync back to OverlayQA?

Yes. Completing an exported to-do in Basecamp marks the OverlayQA issue Resolved, reopening it marks the issue Open, and moving it to the trash or archiving it marks the issue Closed. A comment on the to-do appears on the OverlayQA issue with the commenter's name.

What does a Basecamp to-do from OverlayQA include?

The to-do is named after the issue. Inside it are the issue description, the screenshots, the page URL, a Figma frame link when there is one, the type, severity, browser, OS and viewport, the element selector and CSS values, any AI analysis, the comments present at export time with their files, and an Open in OverlayQA link back to the issue. There is no field picker, so you set assignees and due dates in Basecamp.