This integration provides issue-tracking support to organizations whose development teams use GitHub. Move accessibility tasks from Level Access into GitHub Issues without having to recreate accessibility work in GitHub and maintain information across two systems. For details on how to establish a GitHub connection, and push tasks to GitHub issues, refer to Working with GitHub integration.
Available for: Accelerate, Enterprise, and Essential with the Integrations add-on.
Who can use this feature:
Organization Administrators / Issue Tracking Administrators can create, edit, reauthorize, and remove a GitHub connection.
On this page:
Benefits of integration with GitHub Issues
Use GitHub Issues to manage accessibility remediation through the issue-tracking workflow your development teams already uses.
With this integration, you can:
Connect a Level Access project to a GitHub repository.
Create a GitHub issue directly from a Level Access task rather than recreating the work manually.
Bulk-push tasks to GitHub Issues.
Keep task progress aligned with the GitHub Issue's Open or Closed state.
Keep comments and relevant updates connected between Level Access and GitHub.
See important GitHub Issue information from the linked Level Access task.
Continue using Level Access as the source of accessibility context while development team works in GitHub.
Affected roles
The integration affects the following roles:
Accessibility professionals managing remediation through Projects and tasks.
Developers working on accessibility issues in GitHub.
Organization administrators responsible for configuring issue-tracking integrations.
Workspace administrators and workspace users working with Projects and tasks.
GitHub connection statuses
This table describes the GitHub Issues connection statuses used on the platform.
| Status | Description |
|---|---|
| Authorized | The connection is authorized. All integration functionality should be working as expected. |
| Interrupted | An error has occurred between the platform and GitHub. An attempt to reestablish the connection will be made and if successful, the connection status will return to Authorized. |
| Not authorized |
The platform has received a 401 authorization error for this connection. If authorization is lost, an administrator can reauthorize the connection.
If you’re still experiencing issues, request support. |
Limitations
| Limitations | Details |
|---|---|
| One repository per Level Access project |
A project can only be connected to one GitHub repository. Changing that repository unlinks all existing task-to-GitHub relationships for the project. |
| Repository access is based on the GitHub user's account access | The OAuth connection can expose all repositories accessible to the authorizing GitHub user, including repositories outside a single organization and personal repositories. |
| Reauthorization requires the same GitHub account | You can't reauthorize a connection with a different GitHub account. |
| Synchronization |
|
Attachments use a GitHub-specific approach |
Attachments appear through links in comments rather than as standard native GitHub Issue attachments. |
Frequently asked questions
What authentication does GitHub Issues use?
GitHub Issues uses OAuth. Personal Access Tokens are not supported.
Which GitHub permissions are requested?
The OAuth connection currently requests:
reporead:orgproject
Which repositories will I see?
Level Access retrieves repositories that the authenticated GitHub account can access. This might include public and private repositories across organizations as well as personal repositories.
Can one Level Access project connect to multiple GitHub repositories?
No. A project connects to one GitHub repository.
Can I link a task to a GitHub Issue that already exists?
No. The capability is not available in this release.
Can I configure GitHub dynamic field mapping?
Not in this release.
Does GitHub Issue type work with the integration?
Issue type is not supported at launch.
Does status synchronize?
Yes. GitHub Open and Closed states can be mapped to Level Access task progress values, and mapped changes synchronize in both directions.
Does closing a GitHub Issue resolve the accessibility finding?
The integration updates the mapped Level Access task progress, not the underlying accessibility finding status.
Do comments synchronize?
Yes. Comments synchronize between Level Access tasks and GitHub Issues. Detailed comment deletion behavior and edge cases will be covered in supporting documentation.
Do attachments synchronize?
Attachments are supported, but they are represented as links in GitHub comments rather than standard GitHub-native attachments.
Does title synchronize?
GitHub title changes are reflected in Level Access. Later Level Access title changes are not confirmed to update GitHub.
Does assignee synchronize?
GitHub assignee information is displayed in Level Access and GitHub-side changes are reflected there.
What happens if I change repositories?
All existing task-to-GitHub links for the project are removed. Tasks are not automatically pushed to the new repository and must be pushed again individually if needed.
Are the existing GitHub Issues deleted when the repository or connection is removed?
The GitHub Issues themselves are not deleted. The Level Access relationships are removed.
What happens if authorization expires or is revoked?
The connection becomes Not Authorized and can be reauthorized using the same GitHub account.
Can I reauthorize using another GitHub account?
No. Reauthorization with a different GitHub account is blocked.
Is there a Resync all tasks action?
No equivalent action is currently documented for GitHub.
Does GitHub Enterprise work?
GitHub Enterprise Server is not supported
Comments
0 comments
Please sign in to leave a comment.