GitHub Issues

BugSplat's GitHub Issues integration allows your team to create defects from crash reports with only a couple clicks. Pushing crash reports to GitHub Issues creates hyperlinks in BugSplat and allows for quick navigation from crash reports to your defect tracker and back again. Defects created from BugSplat automatically include symbolic call stack information as well as other crash-specific data.
Integrating GitHub Issues with BugSplat
​Login to your account.
Go to the ‘Settings’ page and under the Defect Tracker tab select GitHub Issues from the drop-down menu.
Enter your GitHub Username, API Token and Repo Owner into the appropriate boxes on the BugSplat ‘Settings’ page.
Select your desired project.
Click Apply.
Creating a defect in GitHub Issues from a BugSplat crash report
Create a new defect from an individual crash report page or a stack key page by using the ‘Create a new defect’ link.
Selecting the ‘Create defect’ link brings you to this page.
Selecting the Submit button will create the defect.
Go to GitHub Issues to view your new issue based on your BugSplat crash report.

Jira

Azure DevOps

Last modified 5mo ago

Copy link

Contents

Integrating GitHub Issues with BugSplat

Creating a defect in GitHub Issues from a BugSplat crash report