Configuration
The fourth tab of the Organization Management panel, available only to accounts with the Admin role. No other role, neither a team manager nor a project manager, opens this tab or changes any of the settings described here. The tab starts with the organization license, and then brings together connections to external systems and the rules by which Q247 calculates and displays data.
The entire tab renders as one long page with successive sections, without sub-tabs. In the documentation, we have split it into separate pages, one per section.
Rollout order
The order matters only at the start of a rollout. Until there is a connection to a data source, the calculation rules have nothing to work on.
- Integrations: connect code repositories, and if the organization uses Jira or Confluence, connect those too. This is the only part of Configuration that requires action on the Customer's systems.
- Flow Metrics and Work calendar: set what the start and end of work on a ticket means for this organization, and which days are working days.
- Exclusions: only once you see the first data will it be clear what distorts the picture and what is worth leaving out.
The remaining sections are independent and can be enabled at any point.
Purpose of each section
Organization license
License is the first section of the tab. It shows the name and expiry date of the license, the organization ID needed when contacting Q247 support, and the number of accounts in the Active status, with and without access, against the limit. A new license key is pasted in the same place.
Connections to external systems
Integrations is a separate subcategory covering connectors to version control systems, documentation integrations (Jira, Confluence, Azure Boards and Azure Wiki), account provisioning via SCIM, and SSO login. You will also find there a page tying together, in order, all the steps needed to get code analysis running.
Metric calculation rules
Flow Metrics set the boundaries of Lead Time and Cycle Time: from which moment counting starts, to which it ends, and which ticket types are included in the calculations. The settings apply to the whole organization, and a single project can override them.
Work calendar covers days off, working hours and time zone. All three settings determine the time from which Lead Time and Cycle Time are calculated, and working hours also serve metrics measured on an hourly basis.
Excluding cherry-pick, revert, rebase and squash ensures that the same work is not counted twice when a commit returns on another branch, gets reverted or lands in the history combined with others through a squash.
File Pattern Exclusions let you skip files that inflate the result without human effort: lockfiles, generated code, build directories.
Visibility and presentation
AI adoption covers the patterns by which Q247 recognizes commits created with the help of AI tools, the widget visibility toggle, and the mapping of telemetry addresses to accounts.
Increment visibility hides, on detail lists, single increments above a set Calories threshold, so that bulk commits do not obscure everyday work.
Email notifications decide whether a newly created account gets an automatic activation email.
Data output
Export CSV for BI downloads the raw data of selected projects for further analysis in external tools.
Side effects and pitfalls
Email notifications and automatic exclusion of cherry-pick, revert, rebase and squash take effect immediately on click, without a save button. The remaining sections require changes to be confirmed.
Some settings also recalculate historical data. This applies to file pattern exclusions, to changes in the Flow Metrics boundaries, and to changes of days off, working hours or time zone in the Work calendar, after which Lead Time and Cycle Time are recalculated for the whole organization. On a large organization, recalculation takes some time, so it is worth settling these settings once, after talking to the people responsible for the process.
Subpages
License
Organization license in Configuration: license parameters and states, the number of accounts taking a seat, and replacing the license key.
Integrations
Q247 integrations with external systems: code repositories, tickets and documentation, identity and sign-in, and the integrations behind AI features.
Email notifications
Email notifications for new users: the organization-wide toggle that sends an activation email right after an account with access is created.
Excluding cherry-pick/revert/rebase/squash
Commit exclusion: automatic skipping of cherry-pick, revert, rebase and squash commits, the recognition rules, and excluding a single commit by hand.
File Pattern Exclusions
File pattern exclusions: glob patterns for files skipped when calculating Calories and Lines, the pattern limits and groups of files worth excluding.
Flow Metrics
Flow Metrics configuration: organization-wide Lead Time and Cycle Time boundaries, their defaults, project overrides and the effect of changing them.
Health Check thresholds
Health Check configuration: enabling health metrics, the five organization-wide thresholds, distribution charts and excluding single repositories.
Work calendar
Work calendar: days off, working hours and time zone shared by the whole organization, used to count Lead Time and Cycle Time in business time.
AI Adoption
AI Adoption configuration: the two data sources on AI usage, commit recognition patterns, the visibility toggle and mapping telemetry accounts.
Increment visibility
Increment visibility: increments above a Calories threshold drop out of statistics, including history, and stay dimmed in increment lists.
Export CSV for BI
CSV export for BI: raw project events, one row per commit or Jira and Confluence change, with the column list, file format, data scope and limits.
See also
- Organization management: the remaining three tabs of the panel
- Permissions: who has access to this tab