RELEASE HIGHLIGHTS
In development for a while — we’re introducing a big new feature.
DEVELOPER PRODUCTIVITY DASHBOARD
One of our most requested features, finally on the roadmap no more.
The request from existing users and potential customers was whether we could analyse developer productivity based on the data we have access to. The technical challenge: could we do this purely from the data within a GIT repository?
What we’ve developed is a unique method of matching developer commit messages against types of activity, then calculating a weighted “Developer Output Score” for each developer — based on contributions by other developers on the same project within the same time period. You can see this data across the following periods
01
Over all time (whether that’s 6 months or 10 years)
02
Over the last 30 days
03
Since your last code replication
04
Each yearly period that we have data for
When viewing data “over all time,” we also highlight each developer’s “Best yearly score” — so you can see if a specific developer had a really high output score in 2023, but hasn’t been so great over the last 30 days, yet is still in the top 5 of all contributors over the entire 5 years of a project.
Single Developer Productivity Dashboard
As well as this, you can access each developer’s own Productivity Dashboard to delve deep into a single developer’s activity and output — what types of activity they’ve been working on, what areas of the code they’ve focused on, and more.
As with everything else, this data can be viewed at the single code vault level, or at the entire combined project level.
This functionality is available to all of our “Partner Pro” subscribers.
OTHER CHANGES
Ability to Configure GIT Provider Integrations at the Project Level
Previously, GitHub or GitLab integrations could only be configured at the overall “Team” level, meaning all projects and code vaults within that team shared the same connections.
These can now be configured at the project level — you can create a project, invite a developer to access only that project, and that developer can manage their own private GitHub or GitLab connection just for that project.
And then in your Project Settings pages, there’s a new “Integrations” tab to connect to GitHub / GitLab.
Auto-Retry Mechanism for Key Facet Analysis
Some of our code analysis is very resource-intensive, and there are rare cases where the analysing process gets stopped by the host machine. We’ve implemented an auto-retry mechanism so the analysis is automatically re-queued before reports are sent and the analysis is marked complete.
FROM COMPLEXITY TO CLARITY
Move from uncertainty to complete code confidence.
Get the independent intelligence you need to understand, verify and protect your software.
Book a demo