Keypup

Dataset: Issues &amp; Pull Requests

Field ID: <code>sprint_name</code>

Description: The name of the attached sprint

The attached sprint is evaluated as such:

If the issue has an <code>ACTIVE</code> or <code>FUTURE</code> sprint (can only have one of the two), then use this sprint.

If the issue only has <code>CLOSED</code> sprints, take the last closed/completed sprint

- If the issue has an <code>ACTIVE</code> or <code>FUTURE</code> sprint (can only have one of the two), then use this sprint.
- If the issue only has <code>CLOSED</code> sprints, take the last closed/completed sprint

The <code>Sprint Name</code> field is the primary identifier for your agile sprints, making it an essential attribute for all sprint-based reporting, from tracking real-time progress to conducting historical retrospectives. As a text field, it is most commonly used for filtering and as a key dimension in your reports.

Filtering for Sprint-Specific Dashboards: The most fundamental use of this field is to scope your entire dashboard or a set of widgets to a specific sprint.

- By applying a filter like <code>Sprint Name = "October Sprint - Week 2"</code>, you can create a focused view to monitor the progress of your current sprint, build burndown charts, and manage the team's workload.
- You can also use regex to analyze a series of sprints, for example, <code>Sprint Name ~ "^Q3 Sprint"</code> to see all work from the third quarter.

Reporting and Velocity Tracking: Using sprint_name as a dimension is the best way to track your team's performance and velocity over time.

- A column chart with <code>Sprint Name</code> as the dimension and <code>SUM(story_points)</code> as the metric will create a classic velocity chart, showing how many story points your team completed in each sprint.

Custom Formulas for Advanced Grouping: If your sprint names follow a consistent convention, you can use custom formulas to group them for higher-level analysis.

- For example, if your sprints are named "Q1 Sprint 1", "Q1 Sprint 2", etc., you can create a dimension with a formula like <code>REGEX_EXTRACT(sprint_name, "^Q\\d")</code> to group your data by quarter, allowing you to see quarterly velocity trends.

- Filtering for Sprint-Specific Dashboards: The most fundamental use of this field is to scope your entire dashboard or a set of widgets to a specific sprint.
 - By applying a filter like <code>Sprint Name = "October Sprint - Week 2"</code>, you can create a focused view to monitor the progress of your current sprint, build burndown charts, and manage the team's workload.
 - You can also use regex to analyze a series of sprints, for example, <code>Sprint Name ~ "^Q3 Sprint"</code> to see all work from the third quarter.
- Reporting and Velocity Tracking: Using sprint_name as a dimension is the best way to track your team's performance and velocity over time.
 - A column chart with <code>Sprint Name</code> as the dimension and <code>SUM(story_points)</code> as the metric will create a classic velocity chart, showing how many story points your team completed in each sprint.
- Custom Formulas for Advanced Grouping: If your sprint names follow a consistent convention, you can use custom formulas to group them for higher-level analysis.
 - For example, if your sprints are named "Q1 Sprint 1", "Q1 Sprint 2", etc., you can create a dimension with a formula like <code>REGEX_EXTRACT(sprint_name, "^Q\\d")</code> to group your data by quarter, allowing you to see quarterly velocity trends.

Issues and PRs > Sprint | Name

Find answers and get help from Intercom Support and Community Experts

This site employs cookies and other technologies that we and our third party vendors use to monitor and record personal information about you and your interactions with the site (including content viewed, cursor movements, screen recordings, and chat contents) for the purposes described in our Cookie Policy. By continuing to visit our site, you agree to our {websiteTermsLink}, {privacyPolicyLink} and {cookiePolicyLink}.

This site uses cookies and similar technologies ("cookies") as strictly necessary for site operation. We and our partners also would like to set additional cookies to enable site performance analytics, functionality, advertising and social media features. See our {cookiePolicyLink} for details. You can change your cookie preferences in our Cookie Settings.

We use cookies to make our site work and also for analytics and advertising purposes. You can enable or disable optional cookies as desired. See our {cookiePolicyLink} for more details.

Advertising cookies are set by our advertising partners to collect information about your use of the site, our communications, and other online services over time and with different browsers and devices. They use this information to show you ads online that they think will interest you and measure the ads' performance. Social media cookies are set by social media platforms to enable you to share content on those platforms, and are capable of tracking information about your activity across other online services for use as described in their privacy policies.

These cookies enable the website to provide enhanced functionality and personalisation. They may be set by us or by third party providers whose services we have added to our pages. If you do not allow these cookies then some or all of these services may not function properly.

These cookies are necessary for the website to function and cannot be switched off in our systems.

These cookies allow us to count visits and traffic sources so we can measure and improve the performance of our site. They help us to know which pages are the most and least popular and see how visitors move around the site.

You have the right to opt out of the sale of your personal information. See our {cookiePolicyLink} for more details about how we use your data.

Your Privacy Choices

We use cookies to enhance your experience. You can customize your cookie preferences below. See our {cookiePolicyLink} for more details.

Cookie Settings

Link, Press control-option-right-arrow to exit

Empty Help Center

Uh oh. That page doesn’t exist.

Disappointed

Neutral

Smiley

Thinking...

Searching through sources...

Analyzing...

Tickets submitted through the messenger or by a support agent in your conversation will appear here.

From:
Github (PRs, Issues)	Repositories: N/A Projects: `Iteration.title`
Gitlab (PRs, Issues)	N/A
Bitbucket (PRs)	N/A
Azure DevOps (PRs, Issues)	N/A
JIRA (Issues)	`sprints(last).name`
ClickUp (Issues)	N/A
Trello (Issues)	N/A

Issues and PRs > Sprint | Name

Reporting Use Cases