Dataset: Issues & Pull Requests
Entity: Issues
Field ID: resolving_pr_last_merged_at
Type: Datetime
Description: The latest merge 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 merge of all PRs at the end of the development.
Source: Calculated
Transformation logic:
Pull Requests: Not applicable. This field will always be
null.Issues: The latest occurrence of all
merged_atfields from resolving pull requests. Thenullvalues are ignored. Anullvalue is returned only if allmerged_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 Merged At field is a critical timestamp that marks the definitive completion of all implementation work for an issue, capturing the moment the very last associated pull request was merged. It is the ultimate "code complete" signal, making it essential for measuring post-development process efficiency.
Measuring the "Code-Complete-to-Issue-Close" Gap: This is the field's most powerful use case. It allows you to precisely calculate the duration of any QA, verification, or release processes that occur after all the code has been merged.
You can calculate this with the custom formula
(closed_at - resolving_pr_last_merged_at) / DAY(). A high value for this metric is a clear indicator of a bottleneck in your final testing or deployment pipeline.
Calculating Total Implementation Duration: For complex issues that require multiple pull requests, this timestamp marks the end of the entire coding and merging effort.
The formula
(resolving_pr_last_merged_at - resolving_pr_first_created_at) / DAY()measures the full span of development, from the first line of code written to the final merge, providing a holistic view of the implementation lifecycle for large features.
Filtering for Recently Implemented Issues: 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 Merged 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.