GitHub Issues
BugSplat's GitHub Issues integration allows your team to create defects from crash reports with only a few 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 and other crash-specific data.
Integrating GitHub Issues with BugSplat
Generate a Personal Access Token (PAT) in GitHub. You may use a classic PAT or a fine-grained PAT, ensuring you set the correct Resource Owner, select the correct Repository, and add Issues Read/Write permissions.
Login to your BugSplat account.
Click the Gear icon (⚙️) in the top right of the page and navigate to the Database Settings page and under Database > Integrations > Defect Tracker > GitHub Issues from the options shown.
Enter your GitHub Username, API Token, and Repo Owner into the appropriate boxes and click Apply.
Select your desired project.
Click Apply once more to complete the integration.
Creating a defect in GitHub Issues from a BugSplat crash report
1. Create a new defect from the crash page or a stack key page by using the Create Defect button.
2. Enter relevant details and click the Submit button to create the defect. You can also enter an existing Defect ID if you'd like to associate a crash or stack key with an existing issue from GitHub.
3. Click the link to view the new GitHub issue created by BugSplat.
Automated Defect Creation
Want to create issues in GitHub automatically for each new crash or crash group? Check out the document on auto-creating defects in your third-party defect tracker tool here.
Last updated