Appearance

Integrations ​

Ybug integrates with your favorite tools and services, so you can manage your feedback and bug reports with your existing processes.

Common settings ​

Most integrations offer the same set of options, so you configure them the same way no matter which tool you send feedback to. Each integration keeps its own settings, so you can set them up differently one by one. You'll find them in your project settings, in the Integrations section: open an integration and click Advanced settings.

Title format ​

Every integration creates an item in your tool: an email, a Jira task, a GitHub issue, a Trello card. You can control how its title is composed, which is handy for scanning, sorting and setting up filters in the receiving tool.

The default title format is [{{project.name}}] #{{report.id}} {{report.title}}, for example "[My Project] #123 Checkout button is broken".

Use the Insert placeholder button above the field to add any of these:

  • {{project.name}} — name of the project
  • {{report.id}} — feedback ID in Ybug
  • {{report.title}} — feedback title
  • {{report.text}} — feedback text (first 100 characters)
  • {{report.priority}} — feedback priority, in uppercase (e.g. HIGH)
  • {{report.type}} — feedback type, in uppercase (e.g. BUG)
  • {{report.user.name}} — name of the reporter (if provided)
  • {{report.user.email}} — email address of the reporter (if provided)

If your project uses custom fields, the Insert placeholder menu lists a placeholder for each of them as well.

TIP

Prefixing the title with a placeholder makes triage much easier. Set the format to [{{report.priority}}][{{project.name}}] #{{report.id}} {{report.title}} and feedback arrives as "[HIGH][My Project] #123 Checkout button is broken", which you can sort or build inbox rules on.

Title format is not available for Slack, Webhooks and Zapier.

Forwarded data ​

Ybug includes the feedback details in the description of the item it creates. Use the Select forwarded data checkboxes to choose what goes in, so your tickets carry exactly the context your team needs and nothing more.

  • Source url — the page the feedback was reported from
  • Reported at — feedback datetime in your preferred timezone
  • Reporter — reporter name and email
  • Rating — feedback rating
  • Net Promoter Score — the NPS score, if you collect one
  • Priority — feedback priority
  • Feedback type — feedback type (Bug, Improvement, Question, Feedback, or any type you define)
  • Location — approximate location (country, region, city), based on the user's IP address
  • User data — custom user data passed to the feedback widget
  • OS — operating system and version
  • Screen size — screen dimensions in pixels
  • Viewport size — viewport dimensions in pixels
  • Browser — browser name and version
  • User agent — user agent string
  • Referrer — referrer URL
  • Console summary — number of console errors, warnings and failed requests
  • Custom fields — values of your project's custom fields
  • Report url — link back to the feedback in Ybug
  • Screenshot image — the screenshot embedded in the description
  • Screen recording — link to the screen recording
  • Attachments — files the reporter attached

Which options you get depends on what the receiving tool supports, so not every integration offers all of them. Some can also attach the screenshot or the console log to the created item as a file.

Automatic or manual forwarding ​

By default, every new piece of feedback is sent to the integration automatically. Uncheck Send to … automatically if you'd rather review feedback in Ybug first and forward only selected items by hand, from the feedback detail page.

Close feedback after sending ​

Check Close report after sending to … if the receiving tool is where you track the work from that point on. Once the feedback is forwarded successfully, Ybug marks it as read and sets its status to Closed, keeping your Ybug inbox down to what still needs attention.