Add Story Points for Task Estimation #667

New Issue

OVERLORD · 2026-02-04T20:46:15+03:00

OVERLORD commented

2026-02-04 20:46:15 +03:00

Originally created by @esamueljsx on GitHub (Mar 16, 2025).

Is this a feature for the backend or frontend?

Frontend

What would you like?

It would be beneficial to introduce a Story Points feature to help teams estimate the effort required for tasks. Many agile teams rely on story points to measure complexity rather than time, making planning and sprint management more effective.

Why is this needed?

Currently, the software lacks a built-in mechanism for assigning effort estimates to tasks. Teams using agile methodologies often rely on external tools or workarounds (e.g., labels, custom fields) to indicate story points, which is inefficient and inconsistent.

Other information

Proposed Solution:

Introduce a Story Points field that can be enabled per board. The feature should allow users to:

Assign a numeric value (e.g., 1, 2, 3, 5, 8, 13, etc.) to each task.
Display story points on task cards for quick visibility.
Filter and sort tasks based on story points.
Include story points in reports for better sprint tracking.

Additional Features (Optional but Useful):

Customizable story point scales (e.g., Fibonacci, linear, T-shirt sizing).
Integration with burndown charts and velocity tracking.
API support for updating and retrieving story points.

Benefits:

Improves sprint planning and backlog refinement.
Reduces reliance on external tools for estimation.
Enhances team members' visibility of task complexity.
Provides better insights into team velocity over time.

Possible Implementation Approach:

Add a numeric field to each task card for story points.
Allow users to toggle the feature on or off at the board level.
Display the story points in the task preview and detail view.
Integrate with existing reporting tools to visualize story point distribution.

Priority Level:

Medium-High: Many agile teams require this feature for better planning and estimation.

Originally created by @esamueljsx on GitHub (Mar 16, 2025). ### Is this a feature for the backend or frontend? Frontend ### What would you like? It would be beneficial to introduce a Story Points feature to help teams estimate the effort required for tasks. Many agile teams rely on story points to measure complexity rather than time, making planning and sprint management more effective. ### Why is this needed? Currently, the software lacks a built-in mechanism for assigning effort estimates to tasks. Teams using agile methodologies often rely on external tools or workarounds (e.g., labels, custom fields) to indicate story points, which is inefficient and inconsistent. ### Other information ### Proposed Solution: Introduce a Story Points field that can be enabled per board. The feature should allow users to: - Assign a numeric value (e.g., 1, 2, 3, 5, 8, 13, etc.) to each task. - Display story points on task cards for quick visibility. - Filter and sort tasks based on story points. - Include story points in reports for better sprint tracking. ### Additional Features (Optional but Useful): - Customizable story point scales (e.g., Fibonacci, linear, T-shirt sizing). - Integration with burndown charts and velocity tracking. - API support for updating and retrieving story points. ### Benefits: - Improves sprint planning and backlog refinement. - Reduces reliance on external tools for estimation. - Enhances team members' visibility of task complexity. - Provides better insights into team velocity over time. ### Possible Implementation Approach: - Add a numeric field to each task card for story points. - Allow users to toggle the feature on or off at the board level. - Display the story points in the task preview and detail view. - Integrate with existing reporting tools to visualize story point distribution. ### Priority Level: Medium-High: Many agile teams require this feature for better planning and estimation.

OVERLORD commented

2026-02-04 20:46:24 +03:00

@valcriss commented on GitHub (Jul 4, 2025):

Indeed, it's a very good idea. So far, we've been using custom fields to display the "story points" on individual tickets, but that doesn't fully meet our needs.
Would it be possible to also display the total number of story points in a column, next to the column's title?
This would help us better prepare sprints, understand the current workload in each column, and ultimately know the total number of completed points.

@valcriss commented on GitHub (Jul 4, 2025): Indeed, it's a very good idea. So far, we've been using custom fields to display the "story points" on individual tickets, but that doesn't fully meet our needs. Would it be possible to also display the total number of story points in a column, next to the column's title? This would help us better prepare sprints, understand the current workload in each column, and ultimately know the total number of completed points.

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: starred/planka#667