Dataset: Issues & Pull Requests
Entity: Issues
Field ID: resolving_pr_first_created_at
Type: Datetime
Description: The earliest creation date among all resolving PRs (via auto-closing keywords). It is only applicable to issues.
It can be used to calculate specific stages of the cycle time. E.g., the time elapsed between the assignation date of an issue and the beginning of the actual start of the development.
Source: Calculated
Transformation logic:
Pull Requests: Not applicable. This field will always be
null.Issues: The earliest occurrence of all
created_atfields from resolving pull requests.
From: |
|
Github (PRs, Issues) | Calculated |
Gitlab (PRs, Issues) | Calculated |
Bitbucket (PRs) | N/A |
Azure DevOps (PRs, Issues) | Calculated |
JIRA (Issues) | Calculated |
ClickUp (Issues) | Calculated |
Trello (Issues) | Calculated |
Reporting Use Cases
The Resolving PR First Created At field is a crucial timestamp that marks the exact moment development work officially begins on an issue. It provides a definitive starting point for the entire implementation phase, making it essential for accurately measuring your team's responsiveness and the duration of your development cycle.
Measuring "Time to Start Development": This is the field's primary use case. It allows you to calculate the time from an issue's creation until a developer starts writing code to solve it.
You can measure your team's "reaction time" or "time to start" with the custom formula
(resolving_pr_first_created_at - created_at) / DAY(). A high average for this metric indicates that issues are sitting in the backlog for a long time before being worked on, which can be a sign of a planning bottleneck or an oversized backlog.
Calculating the Full Implementation Cycle: This timestamp serves as the true start of the coding and review process for an issue.
You can measure the entire duration of development work with the formula
(resolving_pr_last_merged_at - resolving_pr_first_created_at) / DAY(). This captures the complete time from the first line of code written to the final merge, providing a comprehensive view of the implementation lifecycle.
Filtering for Recently Started Work: You can use this field to create reports that focus on issues that have recently entered the development phase.
A filter like
Resolving PR First Created At in the previous 30 dayswill show you all issues that have had development start in the last month, helping you track the progress of new initiatives.