Dataset: Issues & Pull Requests
Entity: Issues
Field ID: sprint_state
Type: Datetime
Description: The status of the attached sprint. Possible values are:
ACTIVEthe sprint is in progress.CLOSEDthe sprint has been closed.FUTUREthe sprint is scheduled to start in the future.
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 State field is a high-level categorizer that tells you whether an issue is part of a sprint that is currently in progress, finished, or planned for the future. Its primary use is for filtering, allowing you to create dashboards and reports that are focused on a specific point in your team's agile lifecycle.
Filtering for Time-Relevant Dashboards: This is the most common and powerful use of the field. You can scope entire dashboards or individual widgets to focus on a specific sprint phase.
Current Sprint View: To build a dashboard for your daily stand-ups, apply a filter where
Sprint State = "ACTIVE". This will show all the work that is part of the ongoing sprint.Sprint Retrospectives: To analyze the results of completed sprints, filter your reports with
Sprint State = "CLOSED". You can then calculate the final velocity or identify spillover.Future Planning: To review your backlog and plan for upcoming work, use a filter where
Sprint State = "FUTURE".
Reporting on Backlog Health: When used as a dimension, this field provides a simple overview of your work distribution across different time horizons.
A pie chart with
Sprint Stateas the dimension and aSUM(story_points)metric can instantly show you the volume of work in your active sprint compared to what's planned for the future, helping you visualize your planning depth.
Advanced KPIs for Capacity Planning: You can use this field in custom formulas to compare your current workload against your planned backlog.
A report with two metrics,
SUM_IF(sprint_state == "ACTIVE", story_points)andSUM_IF(sprint_state == "FUTURE", story_points), can help you assess if your future sprints are over or under-scoped compared to your current capacity.