GitHub (feedback → issues)
Send visitor feedback to GitHub as issues — complete with the screenshot, page URL, browser details, and console log — so your development team picks it up in the workflow they already use.
Connect a repository
- Go to Integrations (account settings). You'll need an admin role, and your plan must include visitor feedback.
- In the GitHub card, click Connect GitHub. You'll be sent to GitHub to install the Turnjo app and choose which repositories it can access.
- After installing, you'll land back on the Integrations page. Pick the repository issues should be filed in, add any default labels, and Save.
Turnjo only ever stores the installation reference — never a personal access token. Issues are opened by the app, and you can revoke access at any time from your GitHub settings.
Manual or automatic
- Manual (default). Open a report on the feedback board and click Send to GitHub. Nothing leaves Turnjo until you choose to send it — good for teams that triage first and promote only the reports worth tracking.
- Automatic. Turn on "Automatically create an issue for every new feedback report" in the GitHub card. Every new report is filed the moment it arrives. Best for lower-volume sites, or when every piece of feedback should land in your backlog.
You can switch between the two at any time.
What ends up in the issue
Each issue includes:
- The visitor's comment as the body, and a title summarizing it.
- Metadata: feedback type, status, the page it was submitted from, browser and viewport.
- The screenshot, embedded inline.
- The captured console log, in a collapsible section.
- A link back to the report on your Turnjo feedback board.
A report is only ever filed once — sending the same report again (or retries behind the scenes) will never open a duplicate issue. Once filed, the report shows a View issue link.
Route a property to its own repository
By default every property files into the repository chosen above. To customize a specific property, open that property's settings → GitHub routing and pick a different repository — and, if you like, its own auto-create setting and labels. Other properties keep using the account default; switch back to Use the account default any time. Use Apply to all properties to copy one property's routing to every property at once. (The connection stays account-wide — routing only changes where and how issues are filed.)
Disconnecting
Use Disconnect in the GitHub card to stop filing issues. To fully remove the app's access to your code, also uninstall it from your organization's GitHub settings.
More docs
Getting Started
Popups
Surveys
Guided Tours
Experiments
Visitor Feedback
Integrations
Team & Account
Billing & Plans
Privacy & Compliance