Got Feedback?

Tell us how we could make the product more useful to you.

Completed

Filter By Unassigned / No-Status

Please add the option to filter comments by "no user assigned" or "no priority set". This would make it much easier to find new comments that haven't been seen / touched by our team yet. Currently, the filters only select filtering by assigned users or set priority, but on a website that has +200 comments, this doesn't really work because we're constantly having to scroll down past 200 comments to get to the newest ones, and if we accidentally click into one of the comments, it resets the scroll position which auto scrolls us back to the top of the list and we have to scroll AAAAALLLL the way back down past all 200 comments again just to finally select and assign a user / priority to the new comments. It's a big pain point.

Image

Nicholas Stine 15 days ago

πŸ’‘

Feature Request

Planned

Auto-Shift Comment Location

Hello! Firstly, we love what you guys have built!! It's totally changed the way we work with clients to collect and implement feedback!! One notable issue, we've noticed that whenever we update the website in a way that causes content to shift positions, the pin stays fixed; it doesn't shift with the updated content. Obviously, the screenshot solves this problem, but it still causes confusion while reviewing comments and changes during client calls. Is there some way to associate the clicked component with a key or ID, instead of just the pixel position and css selector? Either that or a similar solution so that the pin can intelligently shift when the page is altered! Thanks, Nick Stine

Image

Nicholas Stine 25 days ago

1
πŸ’‘

Feature Request

In Review

Demo Walkthrough Mode β€” Pitch before you review

Problem: Today, agencies and product teams pitch work via Loom, Google Slides, or static links, then separately send a BugSmash review link. Two tools, two contexts, friction for both creator and client. Description of Demo Walkthrough Mode: A built-in click-through walkthrough mode inside BugSmash projects. A guided, interactive preview shown to guests before they enter the review/approval flow. Use Case: Agency shares a new website design. Client opens the link, sees a 3–4 step guided walkthrough (hero, key sections, mobile view) with light annotations, then lands directly in the standard comment + approve flow. Why it fits BugSmash: You'd own the full pitch β†’ review β†’ approve loop (no competitor does this today) Reuses your existing workspace, comments, no-login guest flow, and version system How it works: Inside any project, toggle "Walkthrough Mode." Add steps by selecting elements/regions + a short note. Guest lands on walkthrough first, then the review screen. Versioned with the project (no new infrastructure needed).

Image

FT 27 days ago

πŸ’‘

Feature Request

In Review

Localhost Tunneling Integration via SERVEO

Description: A Serveo integration would enable developers to share localhost demos directly through BugSmash without deploying to staging servers. Use Case: As a developer / vibecoder / web designer, it would be beneficial to share my local development environment for review so that I can get feedback faster without uploading/deploying first. How it works: Create project β†’ Select "Localhost" option BugSmash generates secure tunnel (via Serveo.net integration) Share BugSmash link with reviewers Reviewers access localhost through BugSmash's interface Time-limited access (auto-expires after review period) Benefits: Eliminates deployment bottleneck Faster iteration cycles No staging server costs Perfect for rapid prototyping Unique competitive advantage Technical: Serveo provides SSH/WireGuard tunneling without proprietary clients. BugSmash would manage tunnel lifecycle and integrate with existing access controls. Suggested Implementation: Start as opt-in beta feature for Pro users. Clear security warnings. Fallback to traditional upload method. Target Users: Solo developers, small agencies, teams doing rapid prototyping and internal QA. Contact information: 🌐 https://serveo.net πŸ‘€ Serveo founder: Trevor Dixon βœ‰οΈ trevordixon@gmail.com

Image

FT about 1 month ago

4
πŸ’‘

Feature Request

Completed

expose comment location data on the v2 REST API

Hi BugSmash team, We use the v2 API to automate processing of website review feedback (list comments, action the changes in code, post replies). It works well and v2 is a big improvement over v1. One gap is blocking us from fully automating website projects. The per-comment location data is not available on the REST API. Both GET /api/v2/comments?projectId=... and GET /api/v2/comment/{id} return the comment text, status, priority, screenshot URL and replies, but no information about which page or element the comment was pinned to. On website projects comment_by_name and any page reference come back null, so the API alone cannot tell us where a comment belongs. That same data does exist. Your new JSON export (Project > Export > JSON) includes a full location object per comment: "location": { "live_url": "https://example.com/for-professionals/#enquiry", "dom_selector": "main > section:nth-child(2) > ... > a:nth-child(1)", "dom_selector_fallback": "...", "closest_parent_selector": "...", "element_tag": "a", "element_text": "privacy policy", "pin": { "x": ..., "y": ... }, "element_bounding_box": { ... }, "viewport": { ... }, "device": { ... }, "browser": "Chrome", "platform": "Desktop" } With live_url, dom_selector and element_text on the API we could locate the exact element in source directly, with no manual export step. The export is great for a one-off batch, but it is a manual download and is not reachable with our API key, so it cannot drive an automated or scheduled workflow. What we would like: Add the location object to each comment in GET /api/v2/comments and GET /api/v2/comment/{id}, or Gate it behind a parameter such as ?include=location to avoid bloating the default response. Note: we tried ?include=location, ?expand=location and ?with=location on the comments endpoint already. They are accepted but ignored (the response is byte-for-byte identical), so there does not appear to be an existing flag for this. At minimum live_url, dom_selector and element_text would be enough for us, though the full object matching the export would be ideal. Additional improvements No way to mark a comment resolved via the API (the bigger one). PATCH /comment/{id} lists status as editable but only accepts an opaque internal UUID, so every value we can actually send gets rejected. Right now our reply is our own "done" marker, but the client still has to manually click Resolve in the dashboard to move it out of active. If they exposed a plain resolve/status endpoint, we could close the loop fully and stop depending on the client remembering to click. This is arguably more friction day-to-day than the location gap. Tags aren't on the API either (optional). The export has a tags field but GET /comments doesn't. Only worth asking for if you plan to actually use tags to flag "on-hold vs action now" β€” otherwise it's a speculative ask. Your call. Thank you. Chris

Image

Chris about 1 month ago

3
πŸ’‘

Feature Request