Keypup

Dataset: Issues &amp; Pull Requests

Field ID: <code>story_points</code>

Description: The number of estimated story points (implementation complexity) associated with the issue.

The <code>Story Points</code> field is a fundamental metric in agile development, representing the estimated effort or complexity of an issue. In reporting, it is the primary tool for measuring team velocity, managing workload, and improving sprint planning accuracy.

Measuring Team Velocity: This is the most critical use case for this field. By aggregating the story points of completed work over time, you can track your team's throughput.

- Velocity Chart: A column chart with a time-based dimension (like <code>sprint_name</code> or <code>YEAR_MONTH(closed_at)</code>) and a metric with the custom formula <code>SUM(story_points)</code> creates a classic velocity chart. This helps you understand your team's capacity and makes future sprint planning more predictable.

Workload Planning and Distribution: You can use story points to gauge the size of your backlog and the workload on your team.

- Sprint Capacity: A KPI showing the <code>SUM(story_points)</code> for all issues where <code>Sprint State = "ACTIVE"</code> gives you an immediate measure of the total planned effort for the current sprint.
- Workload per Assignee: A bar chart with <code>FLATTEN(assignee_usernames)</code> as the dimension and <code>SUM(story_points)</code> as the metric shows how the estimated effort is distributed among team members.

Filtering for Backlog Grooming: You can create actionable lists to improve the quality of your backlog.

- Find Unestimated Issues: A report filtered where <code>Story Points is null or Story Points = 0</code> will instantly create a "To Be Estimated" list for your planning meetings.
- Identify Large Epics: You can find complex items that may need to be broken down into smaller stories by using a filter like <code>Story Points &gt; 13</code>.

Advanced Analysis by Work Type: You can compare the effort spent on different categories of work.

- For example, you can create a report with two metrics to compare effort on bugs vs. features: <code>SUM_IF(CONTAINS(metatags, "bug"), story_points)</code> and <code>SUM_IF(CONTAINS(metatags, "feature"), story_points)</code>.

- Measuring Team Velocity: This is the most critical use case for this field. By aggregating the story points of completed work over time, you can track your team's throughput.
 - Velocity Chart: A column chart with a time-based dimension (like <code>sprint_name</code> or <code>YEAR_MONTH(closed_at)</code>) and a metric with the custom formula <code>SUM(story_points)</code> creates a classic velocity chart. This helps you understand your team's capacity and makes future sprint planning more predictable.
- Workload Planning and Distribution: You can use story points to gauge the size of your backlog and the workload on your team.
 - Sprint Capacity: A KPI showing the <code>SUM(story_points)</code> for all issues where <code>Sprint State = "ACTIVE"</code> gives you an immediate measure of the total planned effort for the current sprint.
 - Workload per Assignee: A bar chart with <code>FLATTEN(assignee_usernames)</code> as the dimension and <code>SUM(story_points)</code> as the metric shows how the estimated effort is distributed among team members.
- Filtering for Backlog Grooming: You can create actionable lists to improve the quality of your backlog.
 - Find Unestimated Issues: A report filtered where <code>Story Points is null or Story Points = 0</code> will instantly create a "To Be Estimated" list for your planning meetings.
 - Identify Large Epics: You can find complex items that may need to be broken down into smaller stories by using a filter like <code>Story Points &gt; 13</code>.
- Advanced Analysis by Work Type: You can compare the effort spent on different categories of work.
 - For example, you can create a report with two metrics to compare effort on bugs vs. features: <code>SUM_IF(CONTAINS(metatags, "bug"), story_points)</code> and <code>SUM_IF(CONTAINS(metatags, "feature"), story_points)</code>.

Issues and PRs > Story points

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)	N/A
Gitlab (PRs, Issues)	N/A
Bitbucket (PRs)	N/A
Azure DevOps (PRs, Issues)	N/A
JIRA (Issues)	Use `Story Point Estimate` if available, otherwise fallback to `Story Points`. Null if none are defined.
ClickUp (Issues)	`points` (requires the Sprints ClickApp)
Trello (Issues)	N/A

Issues and PRs > Story points

Reporting Use Cases