Manual report forwarding

We have added a manual forward button to report detail pages.

Your feedback reports can be forwarded to many third-party integrations. Ybug currently forwards feedback reports to integrations automatically. If a problem occurs and the integration fails, it is now possible to forward your feedback reports into your integrations manually.

Also, if you enable an integration, you can manually forward any older feedback reports you have in the project. This gives you more control over where reports go and makes it easier to recover from temporary integration problems.

Why manual forwarding is useful

Most of the time, integrations should work in the background. A new report arrives in Ybug, and the connected tool receives it automatically. That is exactly how integrations should feel when everything is healthy.

But real workflows sometimes hit small problems: an access token expires, a third-party service has a short outage, a project board is renamed, or an integration is enabled after reports have already been collected. Manual forwarding gives you a simple recovery path without asking the reporter to submit the same feedback again.

When to use manual report forwarding

The manual forward button is helpful in a few common situations:

• An integration failed temporarily. Fix the integration settings, then forward the report again.
• You connected a new integration later. Send older reports to the newly connected tool when they still need action.
• A report needs to go to another team. Forward it to the integration that matches the next workflow step.
• You are testing an integration setup. Use an existing report to confirm that the destination receives the right data.
• You want more control over noise. Keep automatic forwarding off for some cases and manually forward only selected reports.

How the workflow works

The workflow is intentionally simple:

1. Open the feedback report in your Ybug dashboard.
2. Review the report, screenshot, URL, browser details, and user message.
3. Check that the target integration is enabled and configured correctly.
4. Click the manual forward button on the report detail page.
5. Open the connected tool and confirm that the report arrived where expected.

This is especially useful after correcting integration settings. For example, if a ClickUp list was changed or a Trello board was archived, you can fix the destination and then manually send the affected report again.

Example: forwarding older feedback after enabling Jira

Imagine your team collects feedback in Ybug during the first week of a beta test. A few days later, you decide that confirmed bugs should also live in Jira. Instead of copying each report by hand, you can enable the Jira integration and manually forward the relevant older reports.

The team gets the benefit of structured Jira issues while preserving the original Ybug screenshots and context.

Tips for cleaner forwarding

• Review before forwarding. Make sure the report is still relevant and not already resolved.
• Avoid duplicates. Check whether the report was already sent to the same integration.
• Fix integration settings first. If forwarding failed because of configuration, update the settings before retrying.
• Use manual forwarding for triage. Send only confirmed bugs to your issue tracker and keep general comments in Ybug.
• Keep Ybug as the source report. The integration item is useful for delivery, but the original report still contains the full feedback context.

A safer fallback for integrations

Manual report forwarding does not replace automatic integrations. It gives you a practical fallback when something needs attention, when you are connecting a new workflow, or when you want to resend a specific report. Your feedback stays usable, even if a third-party tool needs a quick reconnect or configuration update.