Ctrlk
Sprinto DashboardAPI Reference
For the complete documentation index, see llms.txt. This page is also available as Markdown.

Github Issues Integration

Integrate GitHub Issues with Sprinto to automate change management evidence collection and sync tickets directly to relevant controls and checks.

The GitHub Issues integration enables Sprinto to automatically sync issue and project management data from your GitHub organisation. This helps you demonstrate that change management processes are followed and that tickets are created, tracked, and reviewed as part of your compliance requirements.

Once connected, Sprinto can:

  • Sync tickets from GitHub Issues.

  • Map tickets to relevant controls and checks.

  • Continuously monitor change management evidence.

  • Auto-update evidence based on ticket activity.

Sprinto checks for GitHub Issues integration

Following are the Sprinto checks available for GitHub Issues integration:

Sprinto check
Required action

No new change management tickets were added in over 30 days

This check activates when no new change request tickets have been added in the last 30 days. The status remains "Passing" if no new change requests are detected for the configured projects.

Change management ticket should have an assignee

This check activates if a change request ticket doesn't have an assigned stakeholder. The status is set to "Passing" if a stakeholder is assigned to the change request ticket.

Ticketing system for change management should be setup

This check activates if no ticketing system is configured for Change Management. The status is set to "Passing" if a ticketing system is configured.

Ateast one change management system should be connected

This check activates if no change management system is configured in your Sprinto account.

The status is set to "Passing" if a change management system is configured.

Before you Begin

Ensure the following prerequisites are met:

  • You are logged in to the Sprinto Admin Portal.

  • You have administrator access to the GitHub organisation you want to connect.

  • You have permission to generate personal access tokens (if using a token-based authentication method).

  • Your GitHub organisation allows third-party integrations.

Set up GitHub Issues integration

Step 1: Navigate to the integration

  1. Log in to the Sprinto dashboard.

  2. Go to Settings.

  3. Ensure you are on the All tab.

  4. In the search bar, type GitHub Issues.

  5. Click Connect.

Step 2: Review permissions and data usage

A drawer opens showing:

  • Controls and checks that will be automated.

  • Permissions required (Full access: Read).

  • Data used by Sprinto, including:

    • Remote ID

    • Name

    • Status

    • Description

    • Collection

    • Assignee

    • Due date

    • Projects

    • Remote created timestamp

    • Remote updated timestamp

    • Users

    • Tickets

    • Tags

    • Ticket type

    • Ticket URL

Review the details and click Next.

Step 3: Confirm setup requirements

In the Setup GitHub Issues Integration drawer:

  1. Review the setup instructions.

  2. Select the checkbox confirming that you have administrator access.

  3. Click Connect to GitHub Issues.

A GitHub authentication pop-up appears.

Authentication methods

You can authenticate using one of the following methods:

  1. Fine-grained personal access token (recommended)

  2. Personal access token

  3. GitHub Issues organisation name

Method 1: Fine-grained personal access token (Recommended)

Step 1: Select authentication type

In the GitHub pop-up:

  1. Select Fine-grained personal access token (recommended).

Step 2: Review access permissions

You will see the read access requested for:

  • Tickets

  • Users

  • Collections

Review the permissions and click Next.

Step 3: Enter username and fine-grained token

You will be prompted to enter:

  • GitHub username

  • Fine-grained personal access token

To generate a fine-grained personal access token:

Ensure the token includes the required read permissions as described in the GitHub guidance.

Enter your:

  • Username

  • Token (paste it into the Password field)

Click Next.

Step 4: Enter organisation name

You will be prompted to enter your GitHub organisation name.

To find your organisation name:

  • Navigate to: [PLACEHOLDER – GitHub organisation settings URL]

Copy the organisation name and paste it into the field.

Click Next.

The integration will be set up and tickets will begin syncing automatically.

Method 2: Personal access token

Step 1: Select authentication type

In the GitHub pop-up:

  1. Select Personal access token.

Step 2: Review access permissions

The read access permissions remain the same:

  • Tickets

  • Users

  • Collections

Click Next.

Step 3: Enter GitHub username and personal access token

You will be prompted to enter:

  • GitHub username

  • Personal access token

To generate a personal access token:

  • Follow the instructions on this page.

Ensure the token includes the required permissions, such as:

  • Repository access (read)

  • Project access (read)

  • Webhook permissions (if required)

Enter your:

  • Username

  • Token

Click Next.

Step 4: Enter organisation name

Enter the name of the GitHub organisation you want to connect.

To locate your organisation name:

  • Refer to: [PLACEHOLDER – GitHub organisation reference URL]

Click Next.

The integration will be configured successfully.

Method 3: GitHub Issues organisation name

Step 1: Select authentication type

In the GitHub pop-up:

  1. Select GitHub Issues Organisation Name.

Step 2: Review access permissions

Review the requested read access for:

  • Tickets

  • Users

  • Collections

Click Next.

Step 3: Enter organisation name

You will be prompted to enter your GitHub organisation name.

Enter the organisation name. Once the field is populated, the Next button becomes active.

Click Next to complete the setup.

What happens after setup

Once the integration is successful:

  • Sprinto automatically syncs tickets from GitHub Issues.

  • Evidence for mapped controls is updated in real time.

  • Change management activities are tracked continuously.

  • Relevant checks reflect the latest ticket status.

Troubleshooting

The “Next” button is disabled

  • Ensure all required fields are populated.

  • Verify that the organisation name is entered correctly.

  • Confirm that the token has not expired.

Authentication fails

  • Confirm that you have administrator access to the GitHub organisation.

  • Verify that the personal access token includes the required permissions.

  • Ensure the token has not expired.

  • Regenerate the token and try again.

Tickets are not syncing

  • Check that the integration status is Active under Settings → Integrations.

  • Confirm that the correct organisation name was used.

  • Reconnect the integration if required.

Kindly get in touch with Sprinto Support if you need any assistance with the integration.

PreviousGithub App Integration
NextGitLab Integration

Last updated