Shouldn't Story Points by summed for Sub-tasks in Insights and total Sprint Points?

[Joao Arruda]

Our team was used to work with Story and Task and reference multiple Tasks in a Story.

A Story is generally written by the Product Owner, whereas the Tasks are then created by the Engineers with the pieces of work necessary to accomplish that given Story.

This is not optimal because we prioritize the work in Story level, so whenever a Story changes position in the backlog, you have to manually reposition all the Tasks related to it so they follow eachother.

To get rid of the behavior explained above, we migrated from using Tasks to using Sub-tasks. Right now, prioritization and backlog organization is perfect: we just need to reorder a Story and all the Sub-tasks will go along. It has also enhanced our vision of Story completion as there's a progress bar on the Story with the amount of Sub-tasks that are already marked as Done.

The problem of switching to Subtasks is that now the tab Insights is not working properly neither in the Backlog nor in the Active Sprint.

As you can see below, our current Sprint is only being considered to have a total of 3 points, despite lots of points in the Sprint Backlog. (The 3 counted points are from a Bug, not a Subtask). This is a problem for Sprint Planning as now the points from Subtasks needs to be summed manually by the team, as well as the Sprint commitment chart is already completely wrong as it is not summing the points correctly.

And if you check the Insights in the Active Sprint, the Sprint burndown considers the points correctly, but the Sprint progress presents the same bug as above.

Do you agree it should be fixed? Can you think of any workarounds for that?

[David Friedrich]

Hi @Joao Arruda ,

this article offers a good and easy solution on how to sum up story points from sub-tasks
https://community.atlassian.com/t5/Automation-articles/New-automation-smart-values-in-Jira-Cloud/ba-p/1402775#

Hope that helps!

[David Friedrich]

Just came across this video guide on how to implement it:
https://community.atlassian.com/t5/Automation-articles/Jira-Automation-Sum-Up-Story-Points-Roundup-Initiatives-gt-Epics/ba-p/1928027

[Joao Arruda]

Hey @David Friedrich , it's unclear to me where you are suggesting the usage of Smart Values, can you share your perspective about it?

[David Friedrich]

Hi @Joao Arruda ,

the second link I shared (

https://community.atlassian.com/t5/Automation-articles/Jira-Automation-Sum-Up-Story-Points-Roundup-Initiatives-gt-Epics/ba-p/1928027)

leads to a page with some video tutorials. The first one shows how to set up an Jira Automation rule that sums up the story points from sub-tasks to their parent issue every time this value changes in one of the sub-tasks.

If you are yet not familiar with the concept of Automation rules please view this guide:
https://support.atlassian.com/cloud-automation/docs/jira-cloud-automation/

[Joao Arruda]

Hey, David! I had the page opened here in my browser for a while and I replied without seeing your additional comment, sorry about that.

It partially solves our problem. We would have to fix some reports we do as the points in a Sprint will be duplicated once we add them to the Story, but I'll suggest to the team.

I'll get back to this thread once I have news.

Thanks for you suggestion!