[Upcoming Webinar] Developing Engineering Talent and Leadership Reserve Your Seat

What We Shipped: 6 New Features for Increased Clarity and Granular Control

News & Updates

What We Shipped: 6 New Features for Increased Clarity and Granular Control

Information about the development process is key in understanding the output of a team. It helps engineering leaders provide actionable feedback that benefits the individuals on their teams, stay out of the details that should be handled at other levels, and advocate for their teams at any given time.

At GitPrime, we strive to provide a complete picture of the development process — and package it in a way that allows you to quickly get the information you care about most, and drill down into metrics when they’re trending above or below the team’s norm.

In the past month, we have released a series of features and improvements that help you cut through distractions and quickly get the information you need.

1. Spot dynamics and move across reports within the same narrative

The overhauled Context Menu is a global feature amongst GitPrime reports that allows you to click on an individual’s name and cut over to their metrics in any of the reports within that menu — so you can view an author’s data from one report to the next, and drill down into specific visualizations, without having to adjust your filters.

Previously, this menu allowed you to “filter by user in” specific reports — so you could jump from one report to the next while still viewing that user. Now, you can also “View Tickets”, “View PRs”, and “View Commits” to get a more granular view of the user’s day or week.

2. Customize or remove the labels in the Developer Snapshot report

Now, you can remove or customize the labels shown in the quadrants of the Dev Snapshot report. This release simplifies the design of the Dev Snapshot report, but you can still turn on the labels (or change them) if you’d like. At GitPrime, we aim to shorten the time to first value and provide customers with limitless possibilities and control in the depth or breadth of the data they want to consume.

In your GitPrime dashboard, click on Settings > Configurations > Report Preferences to cudtomize the labels, or switch them on or off.

3. Filter Targets, Averages, Benchmarks, and more in the Fundamentals Reports

Over the past few months, we’ve made significant improvements to the consistency in both design and filtering options across GitPrime’s website and dashboard of reports. This release brings a similar filtering experience to the Fundamentals reports as seen in many of the other GitPrime reports.

You can now toggle items on or off, including “Trends”, “Average”, “Targets”, “This Week”, and “Benchmarks”. Each filter can provide more context of the team’s progress over time.

4. Meet your new GitPrime sign in page

Other parts of our website and platform have evolved to make it easier for our customers to navigate their data and scale with GitPrime. The newly overhauled sign in page now reflects those changes and helps provides a more consistent experience as customers invite members to their teams in GiPrime.

The sign in page is one of the key touchpoints that every single customer experiences with GitPrime, and overhauling its design is a step among the many improvements we have planned to provide a world-class data exploration experience.

5. “Typical” is now “Median” in the PR Resolution report

Previously the histograms in the PR Resolution report had a label that showed the team’s “Typical” across that metric (their typical Time to Resolve, Time to First Comment, etc.). While this worked and helped represent the team’s ‘normal’ compared to the established target, we heard from a few of our customers that “typical” was too vague a term and was causing some confusion.

We’ve since renamed “typical” to “Median” to increase clarity for customers. As we continue to innovate and deliver insights to engineering teams, we’ll be focused on updating the language and design within our platform to ensure our customer’s success. **

6. Quickly distinguish opened and closed PRs in the PR Resolution report

Using the PR Resolution report is one of the quickest ways to identify long-running PRs. Previously, you could filter to only view PRs that were opened but not yet closed. This functionality still exists, but you can now also quickly scan through all PRs to identify those that are still open — the “closed” PRs are now gray, making it easier to skim over those.


If you’re a GitPrime customer, we’d love to continue hearing your feedback — whether that be by emailing us, chatting in the messenger below, or in discussions with your Customer Success Manager.