Dataset: Issues & Pull Requests
Entity: Issues
Field ID: resolving_pr_last_closed_at
Type: Datetime
Description: The latest closure 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 closing of all PRs at the end of the development (the definition of a closed PR differs from a merged PR).
Source: Calculated
Transformation logic:
Pull Requests: Not applicable. This field will always be
null.Issues: The latest occurrence of all
closed_atfields inherited from the Resolving pull requests. Thenullvalues are ignored. Anullvalue is returned only if allclosed_atvalues arenull.
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 Last Closed At field is a crucial timestamp that marks the completion of all development activity for an issue, capturing the moment the very last associated pull request was closed. This makes it the definitive end-point of the implementation phase, allowing for precise measurement of post-coding processes.
Measuring the "Code Complete to Issue Close" Gap: This is the field's most powerful use case. It allows you to calculate the duration of any steps that happen after the final code is shipped, such as QA, documentation, or release staging.
You can calculate this with the custom formula
(closed_at - resolving_pr_last_closed_at) / DAY(). A high value for this metric is a clear indicator of a bottleneck in your final verification or deployment pipeline.
Calculating the Total Implementation Duration: For complex issues that require multiple pull requests, this timestamp marks the end of the entire coding effort.
The formula
(resolving_pr_last_closed_at - resolving_pr_first_created_at) / DAY()measures the full span of development, from the first line of code written to the last PR being closed, providing a holistic view of the implementation lifecycle for large features.
Filtering for Recently Completed Work: You can create reports to track issues where the development work has just been finalized, even if the issue itself is still open for final verification.
Use a filter like
Resolving PR Last Closed At in the previous 7 daysto get a list of all issues that have just completed their coding phase, which is useful for managing the handoff to QA or release teams.