Keypup

Dataset: Issues &amp; Pull Requests

Field ID: <code>sprint_start_at</code>

Description: The datetime at which the attached sprint is set to start.

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 Start At</code> field is a fundamental timestamp for all real-time and historical sprint reporting, as it marks the official beginning of a sprint cycle. It serves as the primary anchor for burndown charts and for measuring how work progresses from the moment a sprint kicks off.

Filtering for Active and Upcoming Sprints: You can use this field to create reports that focus on current or future work.

- To build a dashboard for the sprint that just began, you can use a filter like <code>Sprint Start At in the previous 7 days</code>.
- To get a view of upcoming work, you can filter for issues in future sprints with <code>Sprint Start At in the next 14 days</code>.

Creating Sprint Burndown Charts: This field is the essential starting point for any sprint burndown chart. It sets the beginning of the time axis, against which all completed work (measured by <code>COUNT()</code> or <code>SUM(story_points)</code>) is plotted, allowing you to visualize if your team is on track to meet the sprint goal by the <code>Sprint End At</code> date.

Measuring In-Sprint Responsiveness: You can use this timestamp to calculate how quickly your team starts working on issues once a sprint has begun.

- A custom formula like <code>(first_commit_at - sprint_start_at) / DAY()</code> can measure the "time to first commit" relative to the sprint's start. A high average for this metric might indicate that there are delays or blockers at the beginning of your sprint, or that issues are being added to the sprint late.

- Filtering for Active and Upcoming Sprints: You can use this field to create reports that focus on current or future work.
 - To build a dashboard for the sprint that just began, you can use a filter like <code>Sprint Start At in the previous 7 days</code>.
 - To get a view of upcoming work, you can filter for issues in future sprints with <code>Sprint Start At in the next 14 days</code>.
- Creating Sprint Burndown Charts: This field is the essential starting point for any sprint burndown chart. It sets the beginning of the time axis, against which all completed work (measured by <code>COUNT()</code> or <code>SUM(story_points)</code>) is plotted, allowing you to visualize if your team is on track to meet the sprint goal by the <code>Sprint End At</code> date.
- Measuring In-Sprint Responsiveness: You can use this timestamp to calculate how quickly your team starts working on issues once a sprint has begun.
 - A custom formula like <code>(first_commit_at - sprint_start_at) / DAY()</code> can measure the "time to first commit" relative to the sprint's start. A high average for this metric might indicate that there are delays or blockers at the beginning of your sprint, or that issues are being added to the sprint late.

Issues and PRs > Sprint | Start at

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.startDate`
Gitlab (PRs, Issues)	N/A
Bitbucket (PRs)	N/A
Azure DevOps (PRs, Issues)	N/A
JIRA (Issues)	`sprints(last).startAt`
ClickUp (Issues)	N/A
Trello (Issues)	N/A

Issues and PRs > Sprint | Start at

Reporting Use Cases