Roadmap
Changelog
Help Center

Got Feedback?

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

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 3 days ago

2
💡

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. 3 days ago

1
💡

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 8 days ago

💡

Feature Request

In Review

Centralized To-Do List for Team and Personal Tasks

It would be extremely helpful to have a centralized task list where I can see: All tasks assigned to me All tasks assigned to my team members The status of each task (open, in progress, resolved) The related project or folder This would make it much easier to manage priorities, track progress across projects, and ensure nothing gets lost in comments or feedback threads. Ideally, this could include: Filters (by assignee, project, status) A simple list or Kanban view Notifications or reminders for open tasks Right now, tasks are distributed across different comments and projects, which makes it hard to maintain a clear overview.

Elia Meierhofer 9 days ago

1
💡

Feature Request

CSS rendering issue on swissmemorial.ch review (unexpected arrows / overlay issues)

In our BugSmash review for swissmemorial.ch, CSS seems to be interpreted incorrectly: unexpected arrow elements appear (e.g., near images/footer) and overlays look wrong. We only use.htaccess (HTTP auth)—no firewall/proxy. Could the scan/capture be affected by the login prompt? Review link: https://hhomepage.bugsmash.io/review/qNxdb

Franziska 16 days ago

1
🐛

Issue

In Review

Bilder einzeln downloaden

Hi Nabil, thank you for quickly adding the download button for images. I’ve noticed that I can now download all images together as a ZIP file. It would be very helpful if there were also an option to download images individually. I often send my clients a selection of images, and if they have to download all of them at once, it makes things more complicated. Many thanks to you and your team.

Elia Meierhofer 19 days ago

💡

Feature Request