Dataset: Issues & Pull Requests
Entity: Pull Requests, Issues
Field ID: closed_at
Type: Datetime
Description: The datetime at which the item was merged or closed
Source: Mixed
Transformation logic: Use the native field when the app provides one. For Jira, Trello and Bitbucket Cloud, the date is calculated as described in the App Mapping below.
App Mapping
Github (PRs, Issues) |
|
Gitlab (PRs, Issues) |
|
Bitbucket (PRs) | Bitbucket Cloud: Calculated: the date of the closing update in the pull request activity |
Azure DevOps (PRs, Issues) | PR: |
JIRA (Issues) | Calculated: |
ClickUp (Issues) |
|
Trello (Issues) | Calculated: the date the card was last archived, or |
Reporting Use Cases
The Closed At field is one of the most important timestamps for performance measurement, as it marks the completion of a work item. It is the endpoint for many cycle time calculations and is essential for tracking throughput and team velocity.
Filtering by Completion Status: The presence or absence of this timestamp is the primary way to distinguish between open and completed work.
Focus on Open Items: To create a report of all work that is still in progress, use a filter where
Closed Atis empty.Analyze Completed Work: To measure performance on finished tasks, filter your reports to only include items where
Closed Atis not empty. You can also scope this to a specific timeframe, such asClosed At in the previous 3 months, to review recent accomplishments.
Calculating Cycle Time and Lead Time:
Closed Atis the definitive "end" point for measuring how long it takes to deliver work.Lead Time for Changes: This critical DORA metric measures the total time from creation to completion. It is calculated with the formula
(closed_at - created_at) / DAY().Time to Resolution: You can measure the time from first assignment to completion with
(closed_at - assigned_at) / DAY(), which helps understand how long the active work phase takes.
Measuring Throughput: By using
Closed Atas a dimension in charts, you can visualize your team's delivery pace.Team Velocity: A column chart with
YEAR_MONTH(closed_at)as the dimension andCOUNT()as the metric will show the number of items your team completes each month. This is a direct measure of your team's throughput.Story Point Velocity: For a more effort-based view of throughput, you can use the same dimension but with
SUM(story_points)as the metric to see the total volume of work (measured in story points) completed each month.
