Dataset: Issues & Pull Requests
Entity: Issues
Field ID: sprint_end_at
Type: Datetime
Description: The datetime at which the attached sprint is set to finish.
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 End At field is a crucial timestamp for forward-looking planning and real-time sprint management, as it defines the official deadline for an active or future sprint. It is essential for tracking progress against your sprint goals and identifying work that is at risk of not being completed on time.
Filtering for Current Sprint Work: The most common use of this field is to create widgets that focus exclusively on the items planned for the currently active sprint.
To build a "Current Sprint" dashboard, you can apply a filter where
Sprint State = "ACTIVE". You can then see all issues and pull requests that are part of the ongoing work cycle.
Creating Sprint Burndown and Progress Reports: This field provides the end date for your sprint, which is a key component for any burndown or progress visualization.
When used in a chart, you can visually track the completion of work against the
Sprint End Atdeadline to see if your team is on track.
Identifying At-Risk Items: You can compare an issue's
due_ondate with thesprint_end_atdate to identify potential planning conflicts.A custom formula dimension like
IF(due_on > sprint_end_at, "At Risk: Due After Sprint", "On Track")can flag issues where the individual deadline falls after the sprint's official end date, which can help you proactively manage expectations and re-prioritize work.