Skip to main content

Issues and PRs > Resolving PR last created at

Tom Williams avatar
Written by Tom Williams
Updated over a week ago

Dataset: Issues & Pull Requests

Entity: Issues

Field ID: resolving_pr_last_created_at

Type: Datetime

Description: The latest creation date among all resolving PRs (via auto-closing keywords). It is only applicable to issues.

Source: Calculated

Transformation logic:

  • Pull Requests: Not applicable. This field will always be null.

  • Issues: The latest occurrence of all created_at fields 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 Last Created At field is a specialized timestamp that marks the moment the last pull request associated with an issue was created. This is particularly useful for complex issues that require multiple PRs, as it signals the start of the final phase of implementation.

  • Measuring the Implementation Window: The primary use of this field is to understand the time span over which development work was spread out.

    • By calculating the difference between the first and last PR creation dates with the custom formula (resolving_pr_last_created_at - resolving_pr_first_created_at) / DAY(), you can measure the duration of the "implementation scope" phase. A long duration suggests that a feature was implemented in several stages over a long period.

  • Calculating the "Final Push" Duration: This timestamp marks the beginning of the last piece of the implementation puzzle.

    • You can measure how long it takes to complete the final part of a feature with the formula (resolving_pr_last_merged_at - resolving_pr_last_created_at) / DAY(). This calculates the time from the creation of the last PR to its merge, showing how quickly the final piece of work moves through your pipeline once it's started.

  • Filtering for Recently Expanded Work: You can use this field to find issues where new development work has recently been initiated, even if the issue itself is old.

    • A filter like Resolving PR Last Created At in the previous 7 days will create a list of all issues that just had a new PR linked to them, which is useful for tracking the progress of large or ongoing epics.

Did this answer your question?