It has been an exciting past three months for GitClear. Most significant has been the release of our v3 dashboard, which created an exponential combination of pages (committers * repos * reports) that can be navigated to get a full, rich picture of repo activity. But with great power comes great responsibility. We've managed to create reports that can answer almost any question that a CTO or VP Engineering would ask about the state of their team. But we hadn't made it clear how to find the most important report for today.

This morning we took a big step toward fixing that. Next time you visit your Highlights page, you will see a collection of the most consequential insights pertaining to your team during the past week. It should look something like this:

A selection of recent events in the Alloy repo

We're starting with the following notification types:

Impact fluctuation

When a developer's last week is under the 20th percentile, or above the 80th percentile, among their past year's worth of weekly Line Impact values. We might tune this down to 10 or 90 percentiles if it proves too noisy.

Story point fluctuation

When a ticket has accumulated 50% more Line Impact than would be predicted by the number of Story Points assigned to its Jira ticket. Only active after specifying a Jira column used for Story Points.

Cohort monthly

For new hires' first three months on the job, generate a link once monthly to keep apprised of how their performance compares to past hires

Prolific helper

Be notified when a committer on the team has invested significant Line Impact during the past week to revising or refactoring a coworker's recently authored code

New domain expert

Triggered on the first month a developer illustrates proficiency in a new-to-them code domain, while also accumulating a significant amount of overall Line Impact (2 days' worth of work) in the domain

Rising bug work

Weekly or monthly Line Impact dedicated to fixing tickets marked as 'Bug' in Jira was more than half of all Line Impact accumulated

Languishing pull request

Triggered on any of the following: (A) PR was opened 4 or more days ago without a comment (B) PR has been open 2 weeks without being merged (C) More than 50% of the work in the PR has taken place after the PR was opened (indicates high degree of rework)

Risky commit

When a developer submits a commit with non-trivial work that was authored at a speed above the 90th percentile of their usual velocity. Rapid code authorship typically lacks testing or polish.

When users log in, they provide their job title, and we try to make use of that to select a thoughtful combination of default notifications for them. For example, those who log in as a "VP of Engineering," will default to receiving emails on Cohort, Impact fluctuation, Domain Expert, and Story Point (if setup) notifications. However, we recognize that the decision about which notifications matter will be a very personal one. To accommodate the widest range of preferences, we're making each type of notification configurable from within the notifications box itself:

Notification settings available from within their display box

If you choose "Dashboard," then we will illuminate the "Highlights" tab when you have unreviewed notifications from that domain.

You can click the notifications individually, or select them en masse:

We then make it easy to unsubscribe or mark as reviewed in one fell swoop. Each notification has a link to be able to review its content in more detail. Also, if you want to unsubscribe from all notifications at once, you can do that via the "Unsubscribe" link at the bottom of the email. No login required for unsubscribe.

linkTell us your burning questions

What are the biggest questions or insights that you wish to extract from your product/development team? There's a good chance that we have the data to answer your question. Notifications are the bridge for us to take relevant insights and deliver them just in time, when the manager needs them most. We'd love to get customer ideas on which notifications to build next!

This content was written in Amplenote. Publish to the web with one click.   Learn more keyboard_arrow_right