Integrations
- Who can connect
- Org admin
- Who can see connections
- Manager, Org admin
- Where
- Admin → Integrations
- Access
- Read-only
DevGlimpse reads from the tools where your work happens and maps everything into one model. A number means the same thing whether a pull request lived on GitHub, GitLab or Bitbucket. Connections are read-only: DevGlimpse never writes to your tools.
What you can connect
| Kind | Provider | What it brings | Connect in app |
|---|---|---|---|
| Code | GitHub | Pull requests, reviews, comments, commits, teams, deployments and Actions workflow runs | Yes |
| Code | GitHub Enterprise Server | The same as GitHub, from your own instance | On the roadmap |
| Code | GitLab (GitLab.com or self-managed) | Merge requests, reviews, commits, teams, pipelines and deployments | Not yet |
| Code | Bitbucket Cloud | Pull requests, reviews and commits | Not yet |
| Tickets | Linear | Issues, states, labels, estimates, teams, projects and cycles | Yes |
| Tickets | Jira Cloud | Issues, issue types, custom fields, boards and sprints | Yes |
| Tickets | Asana | Tasks and their status, read from a custom field named Status | Yes |
| Incidents | PagerDuty | Incidents and services, for incident-based DORA | Not yet |
| Incidents | incident.io | Incidents, for incident-based DORA | Not yet |
| Incidents | Opsgenie | Incidents, for incident-based DORA | Not yet |
| CI | GitHub Actions | Workflow runs and jobs for CI Analytics, and production deploys | Yes, with the GitHub App |
| CI | GitLab pipelines | Pipelines and deployments | Not yet |
Providers marked Not yet work in DevGlimpse today, but their setup screens are not in the app yet.
DevGlimpse also reads AI tool usage over OpenTelemetry. See AI impact.
Connect GitHub
You need to be an owner of the GitHub organization. If you are not, see the last step.
- Open Admin → Integrations and select Add GitHub integration.
- Choose which repositories to track:
- All repositories includes forks and any repository added later.
- All repositories (excluding forks) skips forks in sync and in the dashboards, including forks added later.
- Select specific repositories lets you pick the repositories on GitHub’s install page. GitHub’s own picker decides what DevGlimpse sees.
- Read the permissions list. The App asks for read-only access to metadata, pull requests, commit listings, organization members and teams, deployments and Actions workflow runs. It never reads file contents or diffs. See GitHub App permissions.
- Select Install GitHub App. GitHub opens its install page. Choose the organization and confirm.
- GitHub sends you back and the dialog shows the progress of the 90-day import, Importing your GitHub history. When it finishes it reads GitHub connected.
If you are not an owner of the organization, use Invite your GitHub admin in the same dialog under Not an owner of the GitHub organization?. It creates an invite link you can copy and send. If the App is already installed, use Complete your installation under Already installed the App on GitHub?.
You can change the repository choice later in Repositories synced on each organization’s card. DevGlimpse converges on the new choice. Forks you exclude stay out of the dashboards and their stored rows are kept, so switching back restores them.
Connect Linear
- Open Admin → Integrations and select Add ticket source. You can also use Start on Add Ticket Source in the Setup tasks card on Home.
- Choose Linear and read what DevGlimpse can read: issues with their state, labels and estimates; teams, projects and cycles; and the workspace name. Nothing is requested for writing.
- Select Connect Linear. DevGlimpse sends you to Linear to approve read-only access, then brings you back.
- An org admin of your Linear workspace approves the connection on Linear.
The ticket source then appears in a list with its status and sync progress.
Link tickets to pull requests
A ticket links to a pull request when its key, such as ENG-123, appears in the pull request’s branch name, title or description. For Linear, the pull request that Linear’s own GitHub integration attaches to an issue also links. Linked tickets show planning accuracy and how work flows from ticket to merge.
For Jira Cloud, open Admin → Ticket mappings to review how DevGlimpse mapped your issue types and fields, such as story points, sprint and epic link. Select Read Jira again to re-read the site and keep your edits.
Check or disconnect a connection
- Open Admin → Integrations. Each connection shows a status: Active or Connected, Suspended or Disconnected.
- Select View sync runs to open Admin → Sync runs for the details of each import.
- For a ticket source, select Disconnect and confirm to stop syncing it.
Uninstalling the GitHub App from your organization suspends the connection. Installing it again reactivates it. Notices on Admin → Integrations tell you when permissions are waiting for approval, repositories were removed, a sync is failing or GitHub’s rate limit is deferring a sync.
One person across providers
The same person often has a GitHub login, a GitLab account and a ticket user. DevGlimpse links them into one person automatically when the emails match, and you can merge or split people by hand. See People and identities.
You can also add attributes to people, such as level or location, from a CSV upload, then filter and group reports by them.