GitHub Integration
Learn how to create GitHub issues from inquiries
GitHub integration automatically creates a GitHub issue when an inquiry is converted to a ticket. If your development team manages bugs and requests in GitHub Issues, this helps hand off customer inquiries from support to development
GitHub Integration Setup Flow
1
Subscribe to the GitHub Integration Plan
Subscribe to the GitHub integration plan for the target form from "Billing & Plans"
- GitHub integration is a form-scoped add-on
- Forms without the plan cannot save GitHub integration settings
- After subscribing, the GitHub Issues integration section appears in form settings
2
Prepare a Personal Access Token
Create or prepare a Personal Access Token that can create issues in GitHub
- The token needs write permission for Issues
- Use a token from a user or organization that can access the target repository
- Because the token is stored in QAries, revoke it in GitHub when it is no longer needed
3
Enter GitHub Settings
In "Settings", enter the GitHub owner, repository name, and Personal Access Token in the GitHub Issues integration section
- The owner is the GitHub username or organization name
- The repository field should contain only the repository name
- Leaving the token field blank keeps the existing token unchanged
4
Enable and Save
Turn on "Enable GitHub integration" and save the settings
- Owner and repository are required when the integration is enabled
- If saving fails, check permissions, plan status, and input values
- To pause the integration, turn off the enabled checkbox while keeping the saved settings
5
Test Ticket Conversion
Create a test inquiry, convert it to a ticket, and confirm that a GitHub issue is created
- The inquiry title is used as the issue title
- The issue body includes submitter information, form answers, comments up to conversion time, and attachment information
- If the GitHub API call fails, ticket conversion still succeeds and the failure is logged on the server
6
Define the Workflow
Decide how your team will use the QAries ticket and GitHub issue together
- A GitHub issue is created only once at ticket conversion time, and later replies or status changes are not synced
- Use QAries for customer replies and GitHub for development investigation or implementation work
- If the repository or token changes, save the settings again and run another test
Before You Start
- The target form must have the GitHub integration plan
- You need permission to change form settings
- Confirm the GitHub owner and repository where issues should be created
- Prepare a Personal Access Token with write access to Issues
Security and Operational Notes
- Personal Access Tokens are secrets. Do not paste them into shared chats or documents
- Issue creation happens only at ticket conversion time; QAries replies and status changes are not synced
- When repository names or permissions change, verify the integration again with a test inquiry
What to Do Next
After saving the settings, convert a test inquiry to a ticket and confirm that an issue is created in the expected repository