How to Modify Engineering Metrics Using Keypup’s Custom Formula

Learn how to create custom formulas in Keypup to tailor engineering metrics and reports to fit the unique needs and goals of your organization. Gain more accurate and meaningful insights to make informed decisions and improvements.

Celine Nabais
Celine Nabais LinkedIn
2 min read
How to Modify Engineering Metrics Using Keypup’s Custom Formula

​Customizing engineering metrics can be a game-changer for software engineering organizations. By creating custom formulas, you can tailor engineering metrics and reports to fit the unique needs and goals of your organization, providing more accurate and meaningful insights that help you make informed decisions and improvements. In this tutorial, we'll show you how to modify engineering metrics using Keypup's custom formula feature.

Keypup provides a variety of templates for engineering metrics, reports, and KPIs that you can easily adjust to best suit your needs. The templates are built using custom formulas, but we recognize that not all software engineering organizations are equal, so we haven't hardcoded them. This means you can easily modify the provided templates to create custom engineering metrics and reports without having to start from scratch.

In this tutorial, we'll use the example of modifying the PR Lead Time for Changes metric to show you how to use Keypup's custom formula feature. The initial calculation provides the average time (expressed in days) from creation date to merge date of all pull requests (PRs). We're going to change this calculation to evaluate the average time from the first commit date to the merge date instead.

Here are the steps to modify the engineering metric using Keypup's custom formula:

1. Select the insight you want to modify by clicking on the edit button located on the top left of the insight. In this case, we're modifying the PR Lead Time for Changes metric.

Image

2. Select "Edit insight" from the dropdown menu.

Image

3. On the configuration panel located on the left side of your screen, select the "Configure table" option.

Image

4. Enlarge the "Custom formula" section in the metric column.

Image

5. Edit your formula. In this case, we're going to modify the "created at" field to the "first commit at" field. As you type, Keypup provides you with a list of available fields to choose from.

Image

6. Select your field, in this case: "first_commit_at".

Image

7. You have now modified the starting point of the PR Lead Time for Changes calculation from creation date to first commit date.

Image

8. Click on "Document insight" on your left navigation panel.

Image

9. Modify your insight documentation to best reflect your changes. In this case, we replaced the calculation starting point to reflect our change.

Image

10. Don't forget to "Save" your new metric.

Image

Customizing engineering metrics using custom formulas provides more flexibility and customization, which can lead to more accurate insights and better decision-making. With Keypup's platform, you can easily adjust the formulas and fields used in the calculations, as well as modify the documentation to reflect any changes made.

In conclusion, modifying engineering metrics using custom formulas is a valuable tool for software engineering organizations. By tailoring engineering metrics and reports to fit the unique needs and goals of your organization, you can gain more accurate and meaningful insights, allowing you to make informed decisions and improvements. Give Keypup's platform a try today and see how you can benefit from custom formulas and create custom metrics and reports for your organization.

Ready to Transform Your Analytics?

Join teams already using AI to make data-driven decisions faster than ever.

Most Recent Articles

Data Ownership, Governance, and Inter-Departmental Silos: Who Owns the Definition of a Story Point?

Data Ownership, Governance, and Inter-Departmental Silos: Who Owns the Definition of a Story Point?

Centralizing SDLC data across ten business units exposes a governance vacuum long before it delivers insight: seven competing "story point" scales, four business units with no named data owner, and a workflow taxonomy nobody was ever assigned to define. This isn't a GDPR problem — it's a political and technical negotiation over who owns what data, and who is accountable when a poorly maintained JIRA board quietly skews a portfolio-wide metric. Discover how Keypup MCP makes data ownership, definition consistency, and governance maturity measurable across every business unit.

Stephane Ibos
Change Management and Cross-Functional Alignment: Getting HR, Product, and Marketing to Trust Engineering Metrics

Change Management and Cross-Functional Alignment: Getting HR, Product, and Marketing to Trust Engineering Metrics

Rolling out SDLC analytics across an enterprise takes more than an engineering VP's buy-in. If HR misreads flow metrics in performance reviews, or Product Management keeps demanding features while ignoring system health, the initiative quietly becomes an "engineering-only project" that never earns organization-wide trust. Discover how Keypup MCP builds the guardrails, translations, and cross-functional accountability that make SDLC analytics stick beyond engineering.

Liam Davis
Strategic Vendor Selection and Platform Fatigue: How to Add an SEI Platform Without Adding Another Dashboard

Strategic Vendor Selection and Platform Fatigue: How to Add an SEI Platform Without Adding Another Dashboard

Enterprises already juggle dozens of tools for project management, CI/CD, monitoring, and HR. Before adding a Software Engineering Intelligence platform, IT architects and procurement teams need to weigh true integration cost, training burden, and vendor lock-in risk — not just the license fee. Discover how Keypup MCP delivers engineering insight through the tools your teams already use, with no new dashboard, no new login, and a fraction of the total cost of ownership.

Thomas Williams