Raygun now integrates with BugHerd

Nick HarleyPlugins, Product UpdatesLeave a Comment

Good news Raygunners! As you may have already spotted, the Raygun + BugHerd integration is now live and available inside your Raygun account. BugHerd allows you to capture client feedback, resolve issues and manage projects visually.

This is particularly useful when working with clients or users who are not technical, because they can simply point and click to report issues and give feedback on any part of the application or website that needs attention.

To set this integration up, go to your Raygun.io dashboard, and navigate to an application that you want to integrate with BugHerd. In the side menu on the left, click “Application Settings” and then “Plugins” that appears below it.

bugherdintegration

This will display a list of our current integrations where you can then select BugHerd. Click the Setup tab, and then enter your BugHerd API Token. This can be found by going to your BugHerd account, clicking the ‘Settings’ option in the top menu and then ‘General Settings’. After you’ve entered the API Token in Raygun and hit next, select a project, enable the integration and save.

Raygun and Bugherd Integration

With the BugHerd integration setup, you can now go to any error group in the Raygun application and see the BugHerd icon next to the error name. Clicking this will give you options to create new tasks on BugHerd projects, or attach error groups to an existing BugHerd task, all directly from within Raygun. When working with the item in BugHerd you can jump back and see all the details about the crash too, so you can fix it quickly. bugherd2

And that’s it! Easy huh?

Work with other tools that you’d like to integrate with Raygun? Check out our full list here, or make a suggestion in the forums.

If you want to try this out but don’t have a Raygun account yet, sign up for a 30 day trial now. No credit card required.

Next level software intelligence across your entire stack.

Leave a Reply

Your email address will not be published. Required fields are marked *