Integrations
Q247 does not generate data on its own. Everything visible on the dashboards comes from systems that already run at the Client: code repositories, Jira, Confluence, the identity provider. This part of Configuration handles the connections to them.
Integrations fall into three groups of a different character. The first delivers work data, and without it the platform is empty. The second concerns accounts and sign-in and is optional, because the organization can manage accounts manually. The third supports AI functions: it accepts data about the use of AI tools and provides the language model to the AI Assistant.
Integrations that deliver data
| Integration | What it brings | When it is needed |
|---|---|---|
| Connectors | commits and repository history, from which Calories, Increments and Lines are calculated, and the history of CI/CD deployments | always, this is the foundation of how Q247 works |
| Jira | the history of ticket status changes | when the organization wants to measure Lead Time and Cycle Time |
| Confluence | the effort put into documentation | when documentation is a significant part of the team's work |
| Azure Boards | work on Azure DevOps work items | when the organization tracks work in Azure DevOps Server instead of, or alongside, Jira |
| Azure Wiki | the effort put into documentation in Azure DevOps | when documentation lives in an Azure DevOps Server wiki |
Connectors are a subcategory: one connector corresponds to one version control system, and Q247 supports seven types, from GitLab and GitHub to repositories added manually.
Azure Boards and Azure Wiki share one integration card, switched by a data scope field. Connecting the second of these sources comes down to checking an additional box, without re-entering credentials. Both pages describe the full procedure, so it is enough to open the one that matches the source you are connecting.
Running code analysis is a guide to the whole process, from creating the connector to data appearing on the dashboard.
The order of steps matters more than the details of individual fields. The symptom of skipping one of the steps looks identical to an integration failure: the connector shows an Operational status, and the dashboards are empty.
Identity integrations
These two handle different things and are deployed independently.
| Integration | What it handles | What it does not do |
|---|---|---|
| SSO (OIDC) | sign-in through an external identity provider | does not create accounts |
| SCIM Provisioning | creating, updating and deactivating accounts and teams | has no effect on the sign-in method |
You can deploy one of them, both, or neither. With both at once, the identity provider creates the accounts, and users sign in without a password on the Q247 side. With SSO alone, accounts have to be created manually, otherwise sign-in will not find their counterpart in Q247.
AI feature integrations
Both are optional and independent of each other, and each supports a different AI function.
| Integration | What it handles | Data direction |
|---|---|---|
| AI tool logs | receiving telemetry from AI tools, including Claude Code | to Q247 |
| Language Model | the model powering the AI Assistant | from Q247 to the model |
The first feeds the numbers in AI adoption, the second is responsible for the responses of the AI Assistant. AI adoption also works without telemetry, relying then on commit message trailers.
Actions outside Q247
Integrations are the only part of Configuration that requires actions in other systems. Depending on the scope of the deployment, you will need help from people with the right permissions:
- the version control system administrator: a service account and a token with read access to the repositories covered by the analysis; in some systems the token needs broader permissions, listed on the connector pages and in Token permissions for collecting CI/CD deployments,
- the Jira or Confluence administrator: once, to install the Q247 app (cloud versions) or register the webhook (Data Center), when the connector ingests data through webhooks (Jira, Confluence),
- the identity provider administrator: registering the app for SSO or configuring the SCIM connector,
- the network team: for deployments in which the plugin runs in the Client's infrastructure.
Every integration page has its own prerequisites section with a specific list.
Subpages
Connectors
Connectors to version control systems: how a connector works, token permissions, credentials from environment variables, adding one and diagnostics.
Running code analysis
Running code analysis: five steps from an empty organization to data on the dashboards, from the plugin and connector to projects and account statuses.
Jira
Jira integration for Cloud and On-Premise: ticket data for Flow Metrics, webhooks or API polling, historical data backfill, setup and diagnostics.
Confluence
Confluence integration for Cloud and On-Premise: Calories from pages and comments, webhooks or API polling, historical data backfill and diagnostics.
Azure Boards
Azure Boards integration: Calories from Azure DevOps Server work items, assigned to projects by Area Path prefix, with setup and identity mapping.
Azure Wiki
Azure Wiki integration: Calories from Azure DevOps Server wiki pages, assigned to projects by page path prefix, with setup and identity mapping.
SSO (OIDC)
SSO (OIDC) sign-in through an identity provider such as Entra ID, Okta or Keycloak: fields in Q247, provider setup and user account requirements.
SCIM Provisioning
SCIM provisioning: automatic creation and deactivation of accounts from the identity provider, group mapping to roles and access, setup, token rotation.
AI tool logs
AI tool logs: receiving OpenTelemetry data from AI tools such as Claude Code, through the collector built into the plugin or from Dynatrace.
Language model
Language model for the AI Assistant in three variants: the Client's cloud model, an on-premise model or Q247 infrastructure, with network and data scope.
See also
- Configuration: the other sections of this tab, without external connections
- Enterprise Plugin: the component that handles the data integrations
- Enterprise Plugin security: the scope of data exchanged with Q247