Skip to main content

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. It brings together two different things: 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.

  1. 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.
  2. 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.
  3. 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​

Connections to external systems​

Integrations is a separate subcategory covering connectors to version control systems, Jira and Confluence integrations, 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. Days off affect the calculation of Lead Time and Cycle Time, working hours affect metrics measured on an hourly basis.

Excluding cherry-pick, revert and rebase ensures that the same work is not counted twice when a commit returns on another branch or gets reverted.

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​

Two toggles save without confirmation

Email notifications and automatic exclusion of cherry-pick, revert and rebase 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 and to changes in the Flow Metrics boundaries. 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​

See also​