GitHub Issues
Connect GitHub and file Live, Automate and Accessibility bugs as issues in a repository.
Before you start
You need a GitHub account with write access to the repository where issues should be created, and that repository must have Issues enabled.
Get a token from GitHub
Two kinds work. The classic token is the reliable choice:
Classic token (recommended)
- GitHub → your avatar → Settings → Developer settings → Personal access tokens → Tokens (classic).
- Generate new token (classic), name it TestKase, tick the
reposcope, generate, and copy it (ghp_…).
Fine-grained token
- Personal access tokens → Fine-grained tokens → Generate new token.
- Under Repository access choose All repositories, or select the ones to file into.
- Under Permissions → Repository set Metadata: Read-only and Issues: Read and write. Generate and copy it (
github_pat_…).
A fine-grained token sees only the repositories you selected — and repositories owned by an organization stay invisible until that organization approves fine-grained tokens (Organization → Settings → Personal access tokens). If the repository list comes back empty, that's why. A classic repo token has neither restriction.
Connect it in TestKase
- Open Organization → Integrations → Defects and click Connect on the GitHub Issues card.
- Paste the token and click Connect.
- Choose the repository (
owner/name). Archived repositories and ones with Issues turned off aren't listed. Click Save.
What gets created
An issue in that repository with the report title and the pre-filled details, created by the token's owner.
GitHub's API cannot attach files to an issue. The ticket carries the session link (and, for Automate, the video and log links) instead of the screenshot; the Report-a-bug dialog says so before you file. Every other tracker receives the screenshot.
Troubleshooting
▶Repository list is empty
Fine-grained token with no repository access, or an org that hasn't approved fine-grained tokens; or the account has no repositories with Issues enabled.
Fix: Use a classic repo token, or fix the token's repository access.
▶"Issues are disabled for this repo"
The repository's Issues feature is off.
Fix: Enable it under the repository's Settings → Features.
▶"Your defect tracker rejected the credentials"
Token expired or revoked.
Fix: ⋮ → Reset and reconnect.