Dataset: Issues & Pull Requests
Entity: Pull Requests
Field ID: resolved_issue_last_closed_at
Type: Datetime
Description: The latest closure date among all resolved issues (via auto-closing keywords).
Source: Calculated
Transformation logic:
Pull Requests: The latest occurrence of all
closed_atfields inherited from resolved issues. Thenullvalues are ignored. Anullvalue is returned only if allclosed_atvalues arenull. Resolved issues are issues that are referenced by a resolving pull request.Issues: Not applicable. This field will always be
null.
From: |
|
Github (PRs, Issues) | Calculated |
Gitlab (PRs, Issues) | Calculated |
Bitbucket (PRs) | Calculated |
Azure DevOps (PRs, Issues) | Calculated |
JIRA (Issues) | N/A |
ClickUp (Issues) | N/A |
Trello (Issues) | N/A |
Reporting Use Cases
The Resolved Issue Last Closed At field is a specialized timestamp that captures the completion date of the latest closed issue resolved by a pull request. This makes it a powerful tool for analyzing the final wrap-up of complex features and for auditing the synchronization between your project management and development workflows.
Measuring the "Final Close to Merge" Gap: This field allows you to measure the time between the very last related issue being marked 'Done' and the final code being integrated.
You can calculate this with the custom formula
(merged_at - resolved_issue_last_closed_at) / DAY(). A significant positive value indicates a delay in your release pipeline after all planned work was considered complete. A negative value shows that the code was merged before all associated issues were formally closed, which can be a key finding in a process audit.
Calculating Total Feature Duration: For epics or features that are broken down into multiple issues, this timestamp marks the true completion of all planned work.
You can measure the entire lifecycle of a complex feature with the formula
(resolved_issue_last_closed_at - resolved_issue_first_created_at) / DAY(), giving you an end-to-end duration from the initial idea to the final sign-off.
Filtering for Recently Completed Epics: You can use this field to create reports on large-scale work that has recently concluded.
To review all pull requests that were part of epics that wrapped up in the last month, you could use a filter like
Resolved Issue Last Closed At in the previous 30 days.