Release highlights
This release has been in development for a while and we’re very excited about this one! We’re introducing a big new feature.
Developer Productivity Dashboard
We’ve had this one on the Roadmap for a while as it’s one of our most requested features.
The request from existing users and potential customers was whether we could analyse developer productivity based on the data we have access to. And the challenge to us technically was whether we could 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, and then calculating a weighted “Developer Output Score” for each developer.
What this means is that you can see which developer’s have got the highest output score in a given time period, and the score is based on contributions by other developers on the same project within the same given time period. You can see this data across the following time periods:
- Over all time (whether that’s 6 months or 10 years)
- Over the last 30 days
- Since your last code replication
- 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 on your project in 2023, but over the last 30 days it’s not been so great. Yet again, over the entire 5 years of a project they’re still in the top 5 of all code contributors!
This has proven to be very interesting data and we’re very excited to release this.
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. You can see what types of activity they’ve been working on, what areas of the code they’ve been working on the most 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, integrations with GitHub or GitLab using our native integrations could only be configured at the overall “Team” level. This meant that all projects and code vaults within that team account shared the same GitHub and GitLab connections.
These can now be configured at the project level, which means that 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.
You can now set this in your Team Settings page:
And then in your Project Settings pages, there is 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 process that’s analysing the code gets stopped by the host machine.
We’ve implemented an auto-retry mechanism so that in these cases the analysis is automatically re-queued before the reports are sent out and the analysis is marked as complete.
Want to Learn More?
