Ok, we’re going to get a bit technical here, but bear with us. We promise it will be worth your while. 🧐
We now support all parts of the URL when assigning feedback to projects. This means you can include querystring parameters, hashes, unicode characters, and subdomains when setting up your project’s Website URL as shown below. This is particularly handy if you have several BugHerd projects on the same website.
This seemingly small change enables some great new ways for you to use BugHerd that you might not have previously thought of. Such as…
Often websites use the “querystring” to control which language version of the site a visitor will see. A good example of this is the Sonos’ support website.
Now you can set up a different BugHerd project for each language version of your site, enabling you to invite different translators to each.
Popular platforms like Hubspot, Shopify, and more use the “querystring” to direct users to hidden or “preview” versions of your website. This is particularly useful for getting your clients approval before publishing changes for the world to see.
These URLs might look something like this…
Now you can add these links to your project’s Website URL list so that feedback on those pages are directed to the right project in BugHerd.
If you're creating online learning courses, modules or other course content may also be identified by querystrings. For example, Moodle courses can comprise many pages of content identified with URLs like the one below.
Now you can add these URLs to your project’s Website URL list so that feedback on those courses/chapters/modules/etc are directed to the right project in BugHerd.
Finally, if you use BugHerd on a single page web application, your app may use the “querystring” or “hash paths” to identify what screen the user is viewing.
Now when a user gives feedback on a screen, BugHerd captures the full “hash path” and “querystring” so you can be sure the feedback is pinned to the correct element on the screen.
To find out more about any of this check out our help guide here.
Wondering if this will work for your special use case? Let us know in the comments below or via firstname.lastname@example.org. We’re here to help.
The BugHerd Team
Thanks for subscribing!
Check your inbox to verify your email