Skip to main content

Issues and PRs > Resolved Issue last created at

Tom Williams avatar
Written by Tom Williams
Updated this week

Dataset: Issues & Pull Requests

Entity: Pull Requests

Field ID: resolved_issue_last_created_at

Type: Datetime

Description: The latest creation date among all resolved issues (via auto-closing keywords).

Source: Calculated

Transformation logic:

  • Pull Requests: The latest occurrence of all created_at fields from resolved issues. 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 Created At field is a specialized timestamp that marks the moment the newest issue resolved by a pull request was created. It is particularly useful for understanding the duration of scope expansion and measuring the "last mile" of your development cycle.

  • Measuring the Feature Definition Window: The primary use of this field is to calculate the time span during which a feature's scope was being defined or expanded.

    • By calculating the difference between the first and last issue creation dates with the custom formula (resolved_issue_last_created_at - resolved_issue_first_created_at) / DAY(), you can measure the "scope creep" duration. A long period indicates that a feature or epic was in planning for a long time, with new requirements being added well after the initial work began.

  • Calculating "Last Mile" Lead Time: This timestamp marks the start of the final phase of development, once all requirements are known.

    • You can measure the time from the final requirement to the code merge with the formula (merged_at - resolved_issue_last_created_at) / DAY(). A short duration here suggests that your team is able to implement and deliver quickly once the full scope of work is clear.

  • Filtering for Responsiveness: You can create reports that focus on how quickly your team is responding to the latest requests.

    • To see all recently merged pull requests that resolved a very new issue, you can use a filter like Resolved Issue Last Created At in the previous 7 days. This helps you measure your team's agility in addressing emergent needs.

Did this answer your question?