Keypup Releases New Timestamps, Making SDLC Analytics More Granular Than Ever

We are thrilled to announce the release of 10 new timestamps, making SDLC process analytics extremely precise. These timestamps will allow users to calculate more granularly how much time is spent in each step of the development process, from ideation to production. The new timestamps include:

• First commit at - this field provides the datetime at which the first commit was made on a PR. It is populated based on the creation timestamp of the first commit in the PR or issue.
• Last commit at - this field provides the datetime at which the last commit was made on a PR. It is populated based on the creation timestamp of the last commit in the PR or issue.
• Review requested at - this field tracks the datetime at which the PR review was first requested. It is showcased by observing the datetime at which the requested reviewer's array attribute was first modified. (Note: this timestamp doesn’t apply on data collected prior to connecting to Keypup)
• Review last requested at - this field tracks the datetime at which a PR review was last requested. It is showcased by observing the datetime at which the requested reviewers array attribute was last modified. (Note: this timestamp doesn’t apply on data collected prior to connecting to Keypup)
• First review submitted at - this field provides the datetime at which the first review was submitted on a PR. It is populated based on the submission timestamp of the first PR review.
• Last review submitted at - this field provides the datetime at which the last review was submitted on a PR. It is populated based on the submission timestamp of the last PR review.
• Review rejected at - this field provides the datetime at which a PR was first rejected after a review. It is populated based on the submission timestamp of the first PR review with “request changes” status.
• Review last rejected at - this field provides the datetime at which a PR review was last rejected after a review. It is populated based on the submission timestamp of the last PR review with “request changes” status.
• Review approved at - this field provides the datetime at which a PR first met its minimum approval quota from approving reviews. It is populated based on the submission timestamp of the review that allows the PR to meet its minimum number of approving reviews while no “request changes” review is still active.
• Review last approved at - this field is calculated using the same logic as the “Review approved at” field. The populated date will be different from it only if the PR is rejected and approved again.

These new timestamps will allow users to gain a deeper understanding of the development process by identifying areas where progress is slow or inefficient and where improvement can be made.

Keypup's new timestamps will provide software development teams with the data they need to improve their workflows and increase productivity.

Try out these new timestamps today and accelerate your delivery!