GitHub
Create GitHub issues from Screendesk with captured context and repository fields.
Last updated
Was this helpful?
Create GitHub issues from Screendesk with captured context and repository fields.
Send any bug report or recording to GitHub in a few clicks.
Screendesk adds the capture link and debugging context automatically.
This page covers the manual Send to app action. Folder automations create issues automatically when recordings or bug reports enter a folder.
You need edit access on the Screendesk item.
Connect GitHub from Profile → Integrations.
Each teammate uses their own GitHub account.
Title
Yes
Used as the GitHub issue title.
Description
Yes
Your notes are added above the Screendesk context.
Repository
Yes
The repository where the issue will be created.
Labels
No
Labels load from the selected repository.
Assignees
No
Assignees load from the selected repository.
Milestone
No
Milestones load from the selected repository.
A direct link to the bug report or recording
The source website URL, when available
Device and browser details
The capture timestamp in UTC
A link to developer information in Screendesk
Anything you add in the description goes above the generated Screendesk context.
Click Edit fields in the GitHub modal to show or hide optional fields.
Required fields stay visible.
Your field choices are saved for your GitHub connection.
You must be able to edit the bug report or recording.
Watch-only users cannot connect personal app accounts or send items to GitHub.
Workspace admins can remove GitHub from Profile → Integrations for the whole workspace. Existing issue links stay visible.
GitHub is not in the Send to app menu
Open Profile → Integrations and connect GitHub.
If the button is missing entirely, confirm that you can edit the bug report or recording.
The repository list is empty
Make sure your GitHub account can access the repository you want to use.
Then reconnect GitHub from Profile → Integrations.
Labels, assignees, or milestones do not load
Confirm the selected repository has those options available and that your GitHub account has permission to read them.
Last updated
Was this helpful?
Was this helpful?