Dataset: Issues & Pull Requests
Entity: Issues
Field ID: sprint_closed_at
Type: Datetime
Description: The datetime at which the attached sprint was closed.
Source: App
Transformation logic
The attached sprint is evaluated as such:
If the issue has an
ACTIVEorFUTUREsprint (can only have one of the two), then use this sprint.If the issue only has
CLOSEDsprints, take the last closed/completed sprint
From: |
|
Github (PRs, Issues) | Repositories: N/A |
Gitlab (PRs, Issues) | N/A |
Bitbucket (PRs) | N/A |
Azure DevOps (PRs, Issues) | N/A |
JIRA (Issues) |
|
ClickUp (Issues) | N/A |
Trello (Issues) | N/A |
Reporting Use Cases
The Sprint Closed At field is a historical timestamp that marks when the sprint an issue was part of has officially ended. This makes it an invaluable tool for conducting sprint retrospectives, analyzing team velocity over time, and accurately measuring sprint spillover.
Filtering for Sprint Retrospectives: The primary use of this field is to create reports that focus on the outcomes of a specific, completed sprint.
To review all the work that was part of a sprint that just ended, you can use a filter like
Sprint Closed At in the previous 7 days.
Accurately Measuring Sprint Spillover: This field is essential for identifying work that was not completed within the sprint's timeframe.
You can create a custom dimension to flag "spillover" work by comparing the issue's completion date to the sprint's end date with a formula like
IF(closed_at > sprint_closed_at, "Spillover", "Completed in Sprint"). A high percentage of spillover is a strong indicator that sprint planning needs to be more realistic.
Analyzing Historical Velocity: By using this field as a dimension, you can track your team's completed work sprint-by-sprint, which is more accurate than just using a calendar month.
A column chart with
Sprint Closed Atas the dimension and a metric likeSUM(story_points)will show the velocity your team achieved in each of your past sprints, allowing you to track performance against your planning cycles.