Got Feedback?

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

In Progress

Display Original Image Filename in Photo Reviews

When reviewing image galleries with clients, it would be extremely helpful if the original image filename could be visible to project owners or admins within the photo preview. Currently, clients can simply comment things like "Photo 4" or "I prefer number 12," which is great because it keeps the review process simple for them. However, on the backend, there is no easy way for me to identify which original file corresponds to the selected image. As a result, I have to manually compare and search through all uploaded photos, which becomes very time consuming when working with larger galleries. My suggestion would be: Keep the client experience simple and unchanged. Optionally display the original filename for project owners, admins, or internal team members. Show the filename somewhere within the image preview or in the details panel Alternatively, provide a toggle to show/hide original filenames. This would significantly speed up photo selection workflows, reduce manual work, and make it much easier to identify which images clients have chosen for editing, retouching, or final delivery. For photographers, designers, agencies, and content creators working with large image sets, this would be a major workflow improvement.

Elia Meierhofer 5 days ago

💡

Feature Request

In Review

Edit Uploaded Files later in the process of a version

I have the following usecase nearly in every project all the time: As versioning is not in all cases possible (like if a page is behind a login screen) we use PDFs for commenting. But take it as Commenting PDFs. After screenshottinng a website the team starts to comment. All of a sudden there was an error or a small thing that needed an exchange of the file in the process of reviewing there is no way of changing the file. This is really annoying as i can not tell my clients that i can not change this “small thing” and all the reviewed work will get lost. So eg. in the case of the PDF - sometimes there are additional pages like show the state of a acordeon in an faq open. I see this while working and can not add additional pages to the base pdf. To me that got crucial by now as i had that problem so often in the process. Thanks for putting such a important feature on the roadmap asap. Best regards and stay safe! Carsten

iq310 8 days ago

2
💡

Feature Request

Completed

Issue: Pen Tool Positioning on PDFs

There seems to be a problem with the pen tool when annotating PDFs. When drawing with the pen on a PDF, the actual drawing is not displayed directly at the cursor position, but instead appears a few centimeters above it. This makes precise annotations very difficult and frustrating. Additionally, when changing the PDF view size, for example switching between a smaller and larger PDF window or resizing the view, the annotations no longer stay correctly attached to the PDF itself. The pen strokes shift and appear in different positions than where they were originally drawn. The annotations should remain locked and accurately mapped to the PDF coordinates regardless of zoom level or window resizing.

Elia Meierhofer 13 days ago

3
🐛

Issue

In Review

Per‑asset versioning inside multi‑asset projects

Hi BugSmash team, first of all, I really like your tool and the way projects and versions work for single assets (one website, one PDF, one image, etc.). However, in real client work there is one major limitation for me: handling multiple variants inside one project. Typical use case 1 – Logos When I design a logo, I often present several logo concepts in parallel, for example 5 logo options in one round for the client. I upload all 5 logos so the client can comment directly on them. The client might only request changes on 2 of those 5 logos. If I now upload a “new version” of the project, the entire project gets a new global version number, even though only 2 logos have actually changed. This makes it hard to compare “Logo 2 – old vs. Logo 2 – new” directly on a per‑logo basis, because the versioning is tied to the whole project, not to each individual asset. Typical use case 2 – multiple layout proposals The same happens with website layouts: I might present 3 layout proposals (A, B, C) in one project so the client can compare and comment on all of them. Later I only revise layout B and C, not A. Again, a single project version number for everything is not ideal, and it becomes confusing if we want to do precise before/after comparisons per layout. What I would love to see I would really appreciate a feature that allows per‑asset versioning inside a project when a project contains multiple images (or screens). In other words: A project can hold multiple assets (e.g. Logo 1, Logo 2, Logo 3, Logo 4, Logo 5). Each asset can have its own versions (Logo 2 – V1, V2, V3), with direct visual comparison between versions of that specific asset. The project itself is then more like a “container” for related assets, but the version logic works on the level of each asset, not only on the whole project. From my perspective, this would avoid the need to create a separate project for every single logo or layout variation, which quickly becomes messy for clients. At the same time, it seems conceptually close to what you already do for single‑asset projects with version comparison, just applied per asset instead of globally. Is this something you could consider adding to your roadmap? For agencies and designers who work with multiple concepts in parallel (logo sets, layout sets, visual explorations), this would make BugSmash much more practical. Thank you very much for considering this and for your great support. Best regards,

b00rn 24 days ago

3
💡

Feature Request

In Progress

Make the guest experience login-free — fix buttons that trigger the login pop-up, add an option to hide all login prompts, and fix the banner overlap

Description: When a guest reviewer opens a shared link, they currently encounter login prompts in multiple places — even when "No Signup Required" is enabled. This adds friction and can scare off less tech-savvy or older clients, who get confused by anything that looks like a forced sign-up. It's about client literacy and keeping the guest experience clean. There are three parts to this request: 1. Disable the buttons that trigger the login pop-up (for guests): Currently, clicking "Assign" ("Not Assigned") or "Mark as resolved" (the checkmark) opens the "Log in to stay in the loop" pop-up. The "Set Priority" button already handles this nicely — it's disabled for guests and shows a tooltip ("Set Priority – Contact project owner to update") instead. Please apply the same behavior to Assign and Mark as resolved. 2. Add an option to fully hide login prompts from guests: Project owners should be able to toggle off, at the workspace or project level, all login pop-ups and the persistent login banner shown to guests. The goal: open link → leave feedback, with zero login prompts anywhere. Owners who want to introduce BugSmash account features to their clients can do so on their own terms. 3. Fix the login banner overlap bug (for owners who keep the banner enabled): The persistent "Log in to stay in the loop" banner currently renders behind the large logo (here replaced with a screenshot of “Workspace Settings”), making it hard to read and click/dismiss. It needs proper z-index/positioning so it stays usable when banner display is enabled.

John B. 25 days ago

2
💡

Feature Request

In Review

Feature Request: Automatic Task Assignment via Project Owner + Inline Assignee Selection

As a managing director working across multiple projects, it would be extremely helpful to define a responsible person for each project. Once a project owner is assigned, any feedback or tasks created by me or the client should automatically be assigned to that person. Currently, I have to manually assign each task, which takes time. Additionally, it would significantly improve the workflow if the assignee could be selected directly while creating the task or comment, instead of only being able to assign it after the comment has been submitted (see attached image). This would streamline task management, reduce manual steps, and ensure faster and clearer ownership across the team. Key Benefits: Saves time by removing manual task assignment Ensures clear responsibility for every project Improves team efficiency and accountability Reduces friction in the feedback workflow

Elia Meierhofer 29 days ago

💡

Feature Request