Product update: Comment on feedback!

We have been working hard in the past few weeks to bring some new cool and long awaited features to Ybug’s dashboard. This update is focused on making feedback easier to discuss, easier to review, and easier to move through your team without losing context.

The biggest change is simple: you can now comment directly on feedback reports. If your team already uses Ybug to collect bug reports, website feedback, design notes, or client review comments, this gives you one shared place to talk about each item before deciding what should happen next.

Comment on feedback

You can finally comment on feedback! It is important to share your thoughts and news with your team to keep everyone up to date. You can now comment on feedback to internally communicate with your teammates.

Before comments, a feedback report could easily turn into a separate Slack thread, email conversation, or quick message between two people. That worked for small issues, but it was easy to lose decisions. Someone would ask whether a bug was reproducible, another teammate would answer in chat, and the next person opening the report would not see that context.

Comments solve that by keeping discussion next to the actual report. The screenshot, page URL, browser details, and team discussion now live together.

How to use feedback comments in your workflow

Feedback comments are especially useful during triage. A simple workflow can look like this:

1. Review new feedback and confirm whether it is a bug, feature request, content change, or duplicate.
2. Add a quick internal note with the decision, such as “Confirmed on Safari” or “Waiting for client clarification.”
3. Mention the next step so the team knows whether to fix, assign, close, or move the report to another tool.
4. Keep follow-up questions inside Ybug instead of scattering them across chat and email.

This keeps the feedback report useful even weeks later. When somebody opens it again, they can see not only what was submitted, but also what the team already decided.

Example: a design issue during client review

Imagine a client reports that a headline looks too small on a landing page. The designer opens the report, checks the screenshot, and leaves a comment: “This matches the approved desktop design, but the tablet breakpoint needs adjustment.” The developer then knows exactly what to fix and does not need to ask whether the whole component should change.

That small internal note saves a round of clarification and prevents the wrong fix from being made.

Previous and Next buttons

To make browsing through feedback easier, we have added Previous and Next buttons. This way you can go through feedback reports without having to return to the entire report list.

This is a small improvement, but it makes a big difference when you have a larger batch of reports to review. Instead of opening one item, returning to the list, finding your place again, and opening the next one, you can move through the queue in order.

Tips for faster feedback review

Here are a few practical ways to use comments and navigation together:

• Triage in batches. Open the first new report and use Previous and Next to move through the queue.
• Leave short decision comments. Notes like “duplicate,” “ready for fix,” or “needs design input” are enough.
• Keep technical findings with the report. If you reproduce the issue, add the browser, device, or condition that triggered it.
• Separate internal discussion from external communication. Use comments to align with your team before contacting the reporter.

What is coming next?

This is just a start. We are going to allow some basic formatting and attachments soon. And it will also be possible to reply to your customer in the same way!

We have also fixed many bugs related to security and reliability of our platform. This is all for today, but there are more features to come, stay tuned!