Version 2.4.4 introduces a new Workload component — a team workload heatmap on the Project and Team views that shows the distribution of each person's development effort over time and makes it easier to spot overloads and unevenly distributed work. We have also added the ability to specify which repository branches are included in the analysis, which translates into more precise metrics. The remaining improvements increase the accuracy and consistency of analytical data — including better cherry-pick detection and immediate hiding of commits across all views — and strengthen the security of access to the system.

Below you will find a detailed description of the most important changes.

---

New Features​

Workload — Team Workload Heatmap​

A new analytical component that, on the Project and Team views — directly below the Delivery Tracker chart — shows the distribution of each person's development effort over time. Each row corresponds to one person, each column to a consecutive period, and the intensity of a cell's color reflects the level of activity. As a result, you can see at a glance who is overloaded, where work is distributed unevenly, and how the workload changes over time.

The heatmap adapts to the context: it uses the date range and metric type selected for the whole view, and the time scale automatically switches between a daily, weekly, monthly, and quarterly perspective depending on the length of the period. Hovering over a cell shows the details of that person's activity, and the built-in search and sorting (by name or activity, with active people always on top) let you quickly find the information you need. Larger teams are handled with pagination, and the footer summarizes key statistics — the number of people, business days, and the average and peak workload. The scope of visible people always matches the user's permissions.

We also took the opportunity to unify the existing activity heatmap on the Participant view — the same color scale and a richer detail preview — so that comparing workload across views is consistent.

Selecting Repository Branches Included in the Analysis (beta)​

We have made available, in beta, the ability to specify which repository branches commits are counted from — globally for all repositories and individually for selected ones. This lets you skip, for example, experimental or release branches and obtain a more accurate picture of the team's work. At this stage the feature has no user interface and is enabled at an organization's request; it also requires the latest version of the Enterprise Plugin.

---

Improvements​

• Strengthened authentication and access-control security — a set of fixes that improve the security of login, tokens, and granting permissions in the system.
• Higher accuracy and consistency of analytical data — better cherry-pick detection (only the copy of a commit is marked, not the original) and immediate, consistent hiding of commits across all analytical views.
• Participant view and login improvements — a user without elevated permissions now sees their own OTIF component, the view preserves the "Total Metrics" selection after a refresh, dropdown lists open smoothly, and password recovery for SSO-login accounts shows a clear message.
• Interface polish and technology refresh — minor consistency fixes for tables, charts, and login screens, plus an update of the user interface libraries.

Version 2.4.3 introduces OTIF Retention — a new measure of the durability of development work, showing how much of the code that was produced remains in the repository after 1, 7, 30, and 90 days. The indicator is available on the Participant, Team, and Project views and in tabular reports, giving teams and management a consistent picture of how much of the effort invested actually stays in the product. The release also expands control over the quality of analytical data — with the ability to exclude selected files from Coding Calories calculation — and adds Gitea as another repository source.

Below you will find a detailed description of the most important changes.

---

New Features​

OTIF Retention​

Q247 introduces OTIF Retention — a new measure showing how much of the code that was produced actually remains in the repository after a given amount of time. For four periods — 1, 7, 30, and 90 days (R1/R7/R30/R90) — the indicator reports the percentage of lines from a given commit that survived to that point. High retention means the work is durable and genuinely builds the product, while low retention points to temporary code that is repeatedly rewritten or quickly removed — giving teams and management a new, objective dimension for assessing contribution, alongside the sheer number of changes.

The indicator is available as a dedicated component with a date range selector on the Participant, Team, and Project views, presenting the R1/R7/R30/R90 values for the selected person, team, or project. The same values appear as columns in tabular reports — of projects (Overview, Participant), teams (Teams), and participants (Project, Team) — allowing the durability of work to be compared and sorted across the entire organization; 30-day retention is shown by default, and the remaining periods can be enabled in the table settings. Values are presented on a color scale from lowest to highest retention, so strong and weak areas are visible at a glance, and the measurement remains correct regardless of how branches are worked with (merge, squash, rebase, cherry-pick).

Retention data is calculated by the Enterprise Plugin, so the indicator begins to fill in once it is updated to the latest version. Retention is also calculated for earlier commits, so the historical picture of work durability is available immediately, with no waiting.

Excluding Selected Files from Coding Calories Calculation​

An organization administrator can now specify which files should be skipped during contribution analysis — for example automatically generated files, dependencies, or generated code that distorts the metrics. The configuration is available in the Manage Organization → Configuration panel, where the administrator defines any number of file name or path patterns and can freely add, edit, and remove them. Files matching any pattern are not counted toward Coding Calories or the line count — both in aggregates and on charts; a commit containing both excluded and other files is counted partially, while commits composed solely of excluded files disappear from statistics and analytical views. A change to the patterns takes effect immediately after the configuration is saved. The feature requires updating the Enterprise Plugin to the latest version — it is the plugin that scans the files in commits while applying the defined exclusions.

Gitea as a New Repository Source​

Gitea joins the supported repository sources — both the cloud and self-hosted versions — which the administrator adds in the Manage Organization → Sources panel, authenticating the connection with a username and an access token (Personal Access Token). Gitea repositories are scanned on the same terms as the other sources, so all metrics and analyses work for them without any difference.

History Transfer When Changing a Repository's Project​

After a repository is reassigned to a different project, its existing activity history moves along with it, preserving the rules that route data to the correct projects. As a result, reports stay complete and consistent with the configuration, without manual data cleanup.

---

Improvements​

Automatic Activation Email on Granting Access​

After a user is granted access or an account is created, the system automatically sends an activation message — with a password-setup link for new accounts, or a login link for people who already have a password. The account form shows a note that such a message will be sent, provided automatic notifications are enabled.

AI Assistant in the Interface Language​

AI Assistant responses now match the language set in the interface, so the user receives analysis in their own language without any additional configuration.

Clearer Account Status​

The account status previously labeled "Technical" is now named "Untracked" (Polish: "Pomijany"), which more clearly communicates that the activity of such an account is omitted from analysis.

Clearer Tooltips​

The content of the tooltips describing metrics and commit markers has been updated, including a new description for the cherry-pick marker, making it easier to understand how individual values are interpreted.

Consistent Dropdowns and Filters​

The appearance of dropdown lists and the way values are presented in filters have been unified, so that interacting with filters and selection fields is consistent across the entire product.

More Stable Work Item Synchronization​

Fetching related work items during repository scanning has been improved, so synchronization runs stably and without errors interrupting it.

---

Bug Fixes​

• Selected filters are once again visible in the table filtering field.
• The message of empty commits and of those created through cherry-pick and revert is no longer lost or truncated.
• Exporting tables to a CSV file now works in the Safari browser as well.
• The correct range of email addresses in the "others" tooltip on the Team view.

Version 2.4.2 of Q247 introduces SCIM integration — automatic synchronization of users and teams from identity providers (Okta, Microsoft Entra ID, Google Workspace, and others compliant with SCIM 2.0), with optional control of the ADMIN role and login access on the IdP side. This release also brings detection of cherry-pick, rebase, and revert in repository history with the ability to exclude them from metrics, and a new presentation of the "Others" group in participant tables with an option to copy the list of people. The remaining changes are a series of improvements aimed at making tables and charts, data source configuration, and login screens easier to use, as well as boosting the performance of the Participant view in large organizations.

Below you will find a detailed description of the most important changes.

---

New Features​

SCIM Provisioning — Identity Provider Integration​

Q247 now supports the SCIM 2.0 standard — accounts and teams are automatically created, updated, deactivated, and removed based on events from an identity provider (Okta, Microsoft Entra ID, Google Workspace, or any other SCIM 2.0 system). The identity provider also groups users into teams (each synchronized group appears as a team in Q247) and maintains membership in those teams, while the arrangement of teams in the organization structure (Team Tree), promoting a member to manager, and team-to-project assignments remain on the Q247 side.

The integration is enabled in Manage Organization → Configuration → SCIM Provisioning, where Q247 generates a one-time bearer token and a SCIM endpoint address to configure on the identity provider side; if the token is lost, it can be rotated.

Optionally, an administrator can designate two SCIM groups: one automatically grants its members the ADMIN role (locking the role field on the profile), the other decides which IdP-linked users are allowed to log in — the two mappings are independent of each other.

Users and teams managed by SCIM are marked with a purple "SCIM" badge; for such users the name, email, status, and SCIM team membership fields are locked, while project participation and membership in manually created teams remain editable. The configuration can additionally be narrowed with an allowed IP address list, and all SCIM operations are recorded in the change log with "SCIM" attribution.

Cherry-pick, Rebase, and Revert Detection in Repository History​

Q247 classifies commits resulting from cherry-pick, rebase, or revert and lets you optionally exclude them from activity metric statistics (Coding Calories, Increments, Activity, and others). The mechanism is enabled by the organization administrator via the "exclude cherry-pick / rebase / revert from metrics" flag at the organization level; once enabled, classified commits are marked as excluded, stop counting toward team, project, and participant statistics, and by default no longer appear on the Delivery Tracker chart.

The classification works in two ways: first, based on the commit message — the phrase cherry picked from commit in the body indicates a cherry-pick, and the phrase This reverts commit indicates a revert (with precedence if a commit matches both rules); second, based on the commit identity — if more than one commit with an identical author, author date, and identical list of changed files exists on the same remote, the chronologically first one is treated as the base, and the subsequent duplicates as rebase / cherry-pick.

Analogous logic was run retroactively across the entire base of existing commits, so historical metrics reflect the new classification once the flag is enabled. A single excluded commit can be manually restored to the statistics from the commit details on the chart — excluded entries are also visually highlighted.

New "Others" Group Visualization in Participant Tables​

In the Participants table, once a date filter is applied, the "Others" group is now split into two sub-lists: participants who made at least one increment during the selected period, and those who had no activity in that time. Next to each sub-group's header there is a button to copy the list of email addresses to the clipboard (one address per line), making it easy to quickly extract the set of active or inactive people for further communication outside Q247.

The expandable infotip for the "Others" group has also been visually unified with the Design System mockup — consistent colors, backgrounds, font, and divider.

---

Improvements​

Average by Default on the Delivery Tracker Chart — Team and Project Views​

Upon entering the project and team views, the chart shows the average number of calories and the total calories of all participants. The participant range selection dropdown on the Delivery Tracker chart (Project and Team views) changes the "Top 5 participant" option to "Top 15 participant" — selected by the largest total number of calories in the current date range.

Plugin Editing in Manage Organization​

The name of an existing plugin can now be edited — previously it was set only at creation. The form for adding a new plugin has been simplified by removing fields that were not required for configuration.

Table and Chart Readability in Analytics Views​

Minor improvements to tables and charts: a more readable column layout, filter icons that fit within the layout, improved tooltips and sorting, more precise file names on CSV export, and the elimination of brief chart flickers before the skeleton loader is displayed. The favorites widgets on the home page and favorite teams also work more reliably.

Polish Interface Version​

Completed and unified Polish-language interface translations, along with consistent punctuation in notification messages.

Data Source and Connector Configuration​

Form validation in Sources (including the GIT_MANUAL repository URL and source addresses), duplicates eliminated from the source list, a more readable multibar for bulk operations, and consistent default connector settings for new organizations. Minor layout corrections (Client Secret, the "Not working" badge, the Increment Visibility placeholder).

Login and Account Screens​

Improved validation messages during login and account activation, a more readable layout for the MFA and new-password screens, and a properly positioned GO BACK button.

Manage Organization​

In Edit Member, the account status can now be saved after a change, and an attempt to change a project name to an empty value is blocked with a message. The CSV export from the user list clearly distinguishes between Active and Aliased statuses.

Faster Participant View Loading​

The Participant view loads significantly faster in large organizations. The change covers both the participant card itself and the table of all projects.

Version 2.4.1 introduces Work Dynamics Indexes — five new developer activity indicators (Activity, Presence, Effort, Throughput, Work Rhythm) displayed in participant tables on the Project, Team, Overview, and Teams views. The definition of productive days has also been updated: they are now counted exclusively on business days. This release gives administrators the ability to disable automatic welcome email notifications, users get date synchronization between tables and charts, and everyone gains a quick channel for reporting issues without a separate login.

Below you will find a detailed description of the most important changes.

---

Work Dynamics Indexes — 5 New Developer Activity KPIs​

Participant tables on the Project, Team, Overview, and Teams views now display five new activity indicators. Activity (the average of the other four) is shown as a five-level bar chart with a percentage tooltip, and tables are sorted by this value by default.

• Presence — shows how regularly a participant was active during the selected period. Calculated as the ratio of business days with at least one increment to all business days in the range.
• Effort — measures the intensity of a participant's work. Calculated as the average number of Coding Calories per business day, normalized to a threshold of 50 kcal/day (above this value the coefficient reaches its maximum).
• Throughput — measures the number of increments per business day. Calculated separately for code and documentation, with different normalization thresholds (1 code increment or 10 documentation increments per day = 100%).
• Work Rhythm — shows the regularity of work. Calculated as 1 minus the normalized standard deviation of gaps between a participant's active days — the more regular the gaps, the higher the indicator.
• Activity — a synthetic activity indicator. The arithmetic mean of Presence, Effort, Throughput, and Work Rhythm.

---

Productive / Non-Productive Days Counted on Business Days Only​

Productive Days, Non-Productive Days, and Days Between Increments are now calculated exclusively on business days (Monday–Friday), excluding weekends from the base calculation. This eliminates the underreporting of participant metrics when date ranges include Saturdays and Sundays.

---

Settings in Manage Organization — Welcome Email Toggle​

The Settings tab in Manage Organization gains a new section where an administrator can disable the automatic sending of a welcome email to newly created users — including those created as a result of account aliasing. Emails remain enabled by default, so the behavior for existing organizations does not change.

---

Report An Issue — Submit Issues Without Logging into JIRA Service Management​

A Report An Issue button has been added to the application. It opens the JIRA Service Management portal with the user's email address pre-filled. Requests can be submitted without a separate login to the portal.

---

Default Date Range on Tables and Charts + Date Range Sync​

Tables and charts on the Project and Team views are now synchronized by default in terms of date range — changing the range in one place propagates to the other, and a notice appears on the chart when the range exceeds three months. On participant, team, and project lists, the default table range is the last two weeks.

---

Minor Improvements and Fixes​

• Unified display of user names and emails across all views. Names and email addresses shown in the application are now consistently pulled from the user's organizational profile, eliminating discrepancies previously visible for aliased accounts or accounts with a different login address.
• Filter tooltips + "Last Increment Date" column in the Users view. Filter and table-edit icons now show descriptive tooltips on hover, and the Users table in Manage Organization includes a new "Last Increment Date" column to support decisions about account status.
• Fixes: table column sorting (Polish alphabet and chip columns), first/last name editing for the Member role, a race condition causing 404 errors when switching views quickly, and correct Grade recalculation after changing the Coding/Documentation filter.

Version 2.4.0 is the biggest release in Q247's history. We're introducing Polish language support, the first version of our AI assistant, and we've completely rebuilt the organization management module and the entire permissions system. We've added the ability to assign projects to teams, move repository data between projects, and export CSV data for the entire organization for further analysis in BI tools. The release also includes many smaller UX improvements, bug fixes, and optimizations.

Below you will find a detailed description of the most important changes.

---

Multilingual Support – Polish Language​

We introduced multilingual support in the Q247 platform. As the first additional language, we're making Polish available. Users select the interface language in their profile settings.

The translation covers all key elements of the application – navigation, forms, system messages, and feature descriptions. Technical names remain in English to maintain consistency with source documentation.

---

First AI Assistant in Q247 (Beta, Available for Selected Customers)​

We're launching the first version of Sufler – an AI assistant built into the Q247 platform. The feature works in the context of a selected project and serves as a starting point for the broader AI capabilities we're developing in upcoming releases.

The AI assistant helps managers and application users in their daily work and understanding the data visible in Q247.

---

Rebuilt Organization Management​

We've thoroughly rebuilt the Manage Organization module. The new interface is visually consistent, faster to use, and better reflects the actual structure of work in our customers' organizations.

New Projects Tab (Manage Organization)​

We redesigned the organization's project list view:

• new project table,
• sorting by Project Managers and Users columns,
• a dedicated Assign Project Managers form enabling bulk assignment of PMs to multiple projects at once,
• a form for creating new projects.

New Single Project Management View​

We added a dedicated project management view with Sources and Additional Rules tabs. From this level, an administrator can:

• start, stop, and set the scanning interval for repositories (also as bulk operations),
• assign sources to the project (e.g. Jira, Confluence, GitLab),
• add, edit, and remove Additional Rules, which are used to assign commits to a project based on a pattern in the commit message field,
• rename the project (the change is immediately visible across all views).

New Sources Tab​

We introduced a separate Sources tab in Manage Organization, displaying all data sources in the organization – regardless of which project they are assigned to. From this level, bulk actions are available: starting and stopping scanning, adding new sources, and assigning sources to projects.

New Configuration Tab – Connector Management​

A new Configuration tab has appeared in Manage Organization, where administrators manage connectors to external systems (Jira, Jira & Tempo Cloud, GitLab, GitHub, Bitbucket, Azure DevOps, Gerrit). Forms for adding and editing connectors have been unified, and required fields are clearly marked.

Additionally, we moved the management of other application elements to this tab, such as SSO configuration and defining the calorie threshold above which a commit is automatically hidden.

Managing Organization Structure – Teams Tab​

In the Users and Teams tab, we added the ability to build multi-level team structures with assigning users to nodes and granting roles (Manager / Team Member) at the level of a specific team. We also improved the search functionality in the Assign Team Members and Assign Managers modals – they now support "first name+last name" phrases and display user email addresses.

---

Rebuilt Permissions System​

We redesigned the entire roles and permissions system in the Q247 platform. The new model is simpler, more predictable, and provides greater control over who has access to which data.

Simplified Organization-Level Roles​

We retired the Owner role – its place is taken by a Manager assigned to the root node (_root) in the organizational structure. Users who previously held the Owner role retain full access to business data after migration.

Three Project Roles Instead of Eight​

Instead of the previous eight project-level roles, we introduced three:

• Project Manager – full project management,
• Project Member – access to project data and metrics,
• Viewer – read-only access.

New Viewer Role​

Viewer is a new role for users who need visibility into dashboards and reports without the ability to modify project configuration or data. The ideal role for stakeholders who consume metrics but are not part of the delivery team.

Roles in the Team Structure​

Two roles are available in the team structure: Manager and Team Member. A user can hold different roles in different nodes, allowing precise modeling of actual areas of responsibility within the organization.

New Project Visibility Model – Three Access Paths​

We introduced a consistent project visibility pattern based on three paths:

1. Direct project participation (Project Manager / Member / Viewer),
2. Access through team structure – project assigned to a team to which the manager belongs,
3. Organizational access – through manager assignment in the organizational structure.

Every project created in the organization is automatically visible to users with organizational access, and the Select project dropdown shows only those projects the user actually has access to.

---

Working with Data and Projects​

Assigning Projects to Teams​

As part of the new team structure, you can assign projects to team nodes. This simplifies access management in larger organizations.

Moving Repository Data Between Projects​

We added the ability to move repositories between projects. When changing the assignment:

• all previously scanned events (commits, merge requests, etc.) are automatically reassigned to the new project,
• data in dynamic tables is updated according to the new assignment,
• participants gathered in the repository history are also migrated.

CSV Export with Organization-Wide Data​

We expanded data export capabilities – in the new Integration with BI section, an administrator can download a CSV file containing increments from a selected period for selected projects (or all projects in the organization).

Available options include:

• date range selection (From / To),
• project selection from a dropdown with search functionality and a Select All option,
• a CSV file with a timestamp in the name, correct encoding, and data in tabular format ready for analysis in Excel / Google Sheets / BI tools.

---

Other Improvements​

• Improved calorie calculation for documentation work – we fixed a bug causing incorrect calorie calculation for events where a large amount of content is added at once (e.g. extensive descriptions in Jira tickets, longer entries in Confluence). Applying the fix requires updating the batch plugin on the client side.
• Numeric value formatting – numbers in tables are displayed on a single line with a thousands separator matching the locale.
• Operation confirmations – snackbars confirming the addition/removal of discriminators and sources in the Sources and Additional Rules views.
• Bulk operations in Manage Organization – bulk actions (start/stop scanning, assigning to project, setting interval) now execute on all selected items with progress display.
• Service Desk – a button has appeared in the application with a quick redirect to Jira Service Management, allowing users to submit a problem or inquiry without leaving the platform.
• UX fixes – a series of minor fixes improving daily work with the platform (including visibility of project manager chips, adding a Select All checkbox to tables, refreshing data after profile editing, consistent tab behavior).

The main change in version 2.3.1 is dynamic tables – users can now independently define date ranges and limit the displayed data to a selected period. The feature works across the Overview, Project, Participant, Team, and Teams views. This is a significant extension of analytical capabilities, translating to greater flexibility and control in day-to-day work with data.

The release also brings email address normalization throughout the system – both during login and event collection – eliminating issues caused by case sensitivity. We reorganized the Manage Organization panel into a single tabbed view and introduced a mechanism for automatically hiding increments with extremely inflated values. The release is rounded out with interface and stability fixes.

Below you will find a detailed description of the most important changes.

---

Dynamic Tables​

We significantly expanded the capabilities for working with tabular data across the Overview, Project, Participant, Team, and Teams views.

Date Filter​

A date range filter (From / To) now appears above the tables, allowing users to narrow the displayed data to a selected period. The filter works in sync with charts – hiding events on a chart also updates the data in the table.

Attribute (Column) Selection​

Users can independently decide which columns are visible in the table. The configuration is intuitive and accessible directly from each view.

---

Email Address Normalization (Case Insensitive)​

We unified the handling of email addresses throughout the system – from login, through account creation, to collecting events from repositories.

Login​

Email addresses entered during login are now treated without case sensitivity. Entering Jan@Company.com, jan@company.com, or JAN@COMPANY.COM all lead to the same account – the system always recognizes the user correctly.

Account Creation​

Newly created accounts – both automatic (e.g. from integrations) and manually created by an administrator – are immediately registered with the email address in lowercase format. This eliminates situations where the same person appeared as separate accounts in the system due to different letter casing in the address.

Event and Commit Collection​

When scanning events from version control systems, the author's email address is saved in lowercase format. As a result, commits and events are correctly assigned to existing accounts, regardless of how the address was recorded in the source.

---

Automatic Hiding of Increments​

An administrator can now configure a calory threshold above which an increment is automatically hidden. This mechanism allows the elimination of increments with extremely inflated values without manual intervention.

---

Organization Management in a Single View​

Previously, the Manage Organization section was divided into separate subpages accessible from a submenu.

In version 2.3.1, all views have been consolidated in one place and are accessible via tabs:

• USERS – user management
• TEAMS – team management
• PROJECTS – project configuration
• SOURCES – repository and data source management
• PLUGINS – plugins
• ADDONS – extensions
• CONFIGURATION – organization settings

Navigation is faster and more transparent – all administrative options are available at a single address.

---

Fixes and Improvements​

Release 2.3.1 includes a number of user interface fixes and bug fixes reported after the previous version. We continue the process of systematically improving the application, enhancing visual consistency, component behavior, and view stability.

In version 2.3.0 we focus on further strengthening security and standardizing the authentication process (SSO – OIDC), improving the ergonomics of working with tables and filters, and extending integrations with new version control systems. We have introduced support for Gerrit and Bitbucket integrations, enabling data processing from additional repository sources. We have also expanded table data capabilities, allowing data export with active filters and sorting applied. This release includes both infrastructural changes and significant UX improvements that contribute to greater application consistency and day-to-day workflow comfort.

Below you will find a detailed description of the most important changes.

---

Safer and simpler login (SSO – OIDC)​

In this version we refined login scenarios, especially for organizations using Single Sign-On mechanisms (a login standard that allows using one corporate account across multiple systems), e.g. Okta, Keycloak, Microsoft Entra ID.

SSO Configuration​

An administrator can configure SSO login in:

MANAGE ORGANIZATION → Auth configuration → Edit

Required data:

1. Discovery URL
2. Client ID
3. Client Secret

The configuration is available exclusively for organization administrators.

Additional security measures for organizations using SSO

In organizations where SSO login is active:

• users cannot set or change their password from within the application (both in My profile and in the Users view),
• sending password reset emails is blocked,
• password management is handled exclusively by the Identity Provider (IdP).

This eliminates the risk of inconsistencies between Q247 and the external authentication system.

Streamlined PASSWORD login process

We updated the standard password login flow:

• login,
• password,
• MFA

Each step is performed as a separate stage, improving the clarity and security of the process.

---

Improved table and filter experience​

A significant part of this release was dedicated to improving the ergonomics of filtering, sorting, and browsing data.

Numeric filters​

• Numeric fields now prevent letter input.
• This reduces validation errors and improves filtering precision.

Date filters (From / To ranges)​

Date ranges are now inclusive:

• records with a date equal to the From or To value are included in the results.

This ensures consistency with user expectations when working with time ranges.

List and text field filtering​

Users can:

• search for a value in the dropdown,
• select one or multiple items,
• filter the table based on the selected values.

Search normalization and logic​

We implemented unified query processing logic:

• trimming leading and trailing spaces,
• reducing multiple whitespace characters to a single space,
• case-insensitive search,
• multiple words treated with AND logic (a record must match all query tokens).

---

Table data export​

Users can export data in exactly the scope currently visible in the table (with active filters and sorting applied).

Data is exported to a CSV file, with column layout matching the table view, enabling easy import and further analysis in external tools (e.g. spreadsheets or reporting systems).

---

New integrations and expanded data sources​

In version 2.3.0 we expanded system integrations.

Bitbucket​

We added Bitbucket integration support, so that:

• commits,
• repository events

can be processed and presented in Q247.

Gerrit​

We also extended integrations to include Gerrit – a code review and change management system for Git repositories. Events and commits from Gerrit can now be included in Q247 analyses.

---

UX and communication improvements​

View changes

• The PARTICIPANTS view has been removed. The same data is now available in: TEAMS → team → entire organization (/team/_root)

Unified validation messages

• Messages are more readable and visually consistent.

Activation email update

We updated:

• the email subject,
• the way the Q247 name is highlighted,
• the presentation of the activation link.

Communication is now clearer and more consistent.

---

Performance improvements​

Code repositories

The view runs smoothly even with a large number of repositories.

Worklogs

The worklogs table loads faster, significantly improving the work experience.

In update 2.2.4, we focus on improving data visibility, increasing work intuitiveness, and introducing new tools that facilitate project, team, and user management. We have introduced improvements in statistics presentation, navigation, chart and table personalization, as well as enabled administrators to independently create employee accounts within the organization. Below you will find a detailed description of all changes.

Ability to Create New User Accounts by Administrator​

In the Users view, we added the "Create new user" function, which allows administrators to create accounts for users.

The form includes all key data (email, first name, last name, status, roles, position, seniority, phone, tags).

The system sends an activation email and validates data.

How to Add a New Account?​

To add a new account in the administrator panel, follow these steps:

• Go to the application page and navigate to the Manage Organization section (available in the header).
• Select the Users tab.
• After opening the user list, click Create an account.

Managing User Permissions in the Organization​

We introduced the ability to grant and modify user roles directly in the organization panel. It is now possible to manage Owner, Admin, and Member roles.

Setting User Password​

An Administrator or Owner can now activate user access and enforce password setup through automatic sending of the "Activate your account" message. The user receives a unique link valid for 48 hours and sets the first password independently.

Hiding Increments from Jira​

We added the ability to hide selected increments from Jira. Users can restore hidden items at any time, which allows for increased analysis accuracy and better control of data visibility. The feature facilitates browsing change history by eliminating irrelevant or erroneous information noise.

Simplified Column Selection in Tables​

We have grouped the statistics (Calories, Lines, Increments, Additional Information) in the table management section.

Thanks to this, users can find needed data faster and more efficiently adjust the table layout to current analysis. Both selecting all statistics at once and group or individual selection are available, depending on needs.

Added Chart in Teams View​

In the team view, we added a chart presenting the work of team members, similar to the project view.

The data range (Calories /Increments /Lines), data source, and presentation form (raw data /trend) are variable. This facilitates team work analysis and activity comparison over time.

Improved Section Order in Participant View​

The participant view has been changed to present data from most general to most detailed.

We added section headers and clearly separated data from the selected project from work on other projects. This facilitates orientation on the page and allows faster analysis of key data.

Remembering Settings​

All charts present data in raw data mode by default instead of trend.

The system remembers user selection for each view separately. Thanks to this, data analysis is consistent with user preferences.

Remembering Table Settings​

Tables remember visible columns, active sorting, and view layout for each user and view separately.

After refreshing the page or returning to the view, the system restores user preferences. This streamlines analytical work and eliminates the need for reconfiguration.

Tooltips in Tables​

We introduced tooltips explaining the meaning of data in tables, which appear only when the name is truncated. Thanks to this, users understand presented statistics faster, and the interface is more readable and clear. The solution facilitates data analysis and onboarding of new users.

In this release, we focused on fixing various bugs to enhance the stability and reliability of the system. We also introduced new features and improvements to enhance overall user comfort.

New features and improvements​

• Display of calories from work performed in Jira DC.
• Display of calories from work performed in Confluence DC.
• Display of logged working time on tasks.
• Addition of discriminator functionality.

In this release, we focused on fixing various bugs to enhance the stability and reliability of the system. We also introduced new features and improvements to enhance overall user comfort.

New features and improvements​

• Automatic account locking after an extended period of inactivity.

User view – User management​

• Expanded user account details and editing view with system access.
• Added the ability to manage aliases.
• Added the ability to manage blocked users.