How to Roll Up Story Points from Subtasks to the Parent

[@11174071]

it is working! thank you so much! I've added the sum "Story Points" to the parent Task (not to the Story, like you did - but it still woking)

[@YanraOnesja]

Grt tip!

[@ApetechTechTutorials]

Thanks!

[@hilarywillis741]

Hi Alex! Does this affect any of the reports available in Jira? Will the US points be counted in addition to the sub task points?

[@sauravrajeev]

{{issue.subtasks.Story Points.sum}} - The code.

[@ApetechTechTutorials]

That's all you need!

[@AndriiKupriianov-f9d]

How can I do this for Original estimate field?

[@AndriiKupriianov-f9d]

I don't see filed story points in subtasks in company managed project

[@AndriiKupriianov-f9d]

I don't see field story points in subtasks. I have company managed project, also have it in configuration but don't have it to fill in in subtask

[@varuna4635]

Thanks for sharing this. However at the subtasks level, we don't see an option to define the story points. What could we be missing?

[@Dmytro_Haranzha]

Thank you very much, Alex! Excellent video as all another on your Chanel! But let's imagine the situation that the Story points field of the Parent Story already contains some value, for example 20. After some time, 2 subtasks were created inside the Story to which the values in the Story points field were also added, for example 5 and 10. What the result of the automation rule we will get: - Automation will not work, - Automation will replace the original value of 20 with the sum of Story points of 2 subtasks (15+5). - Automation will show the sum of the initial value and two subtasks (20+10+5)?

[@ApetechTechTutorials]

Automation will replace the original with summation of the subtasks. . . you want to make a decision and go one way or another. You can't have your cake and eat it as well.

[@riccardo8002]

How do you handle when the summation don't match the modified Fibonacci sequence or when the numbers get too large? A possibility when its too large is to break the story up into two or three depending on the size but then you sit with a massive amount of stories. In addition, when you break up the stories you loose the traceability of the tasks in the other stories which was originally in the main story, again there is a workaround by linking the stories but isn't there a more attractive way?

[@sumeetbakshi7636]

In my understanding, story points are relative terms. If subtasks are assigned to different team members. They might have different estimation of same story point. Let’s say story point 3 is medium complexity of work for one but low complexity/ effort for another team member. Is it advisable to add these story point to roll up?

[@vandanaathani7560]

Hi , Do we have same solution for Azure DevOps?

[@praveenkumartupakula8820]

Hi, Thanks for your help, is it possible to sum story points in Fibonacci series, please share the code. Thanks, Praveen.

[@Anna-kc6ll]

Hi! Thanks for sharing! I copied the entire code and follow the steps to the dot. Unfortunatelly, the automation does not work for me :( Pity, bc it would be benefitial.

[@debimohanty1]

Great tip!! but a question, if I delete/remove a sub-task then it should also recalculate the story point right? for me it is not happening, Flow: Added automation-> changed the stroy point in sub-task--> successfully reflects Flow: Delted subtask --> story point in Story does not change to None/0 again

[@jubinabenny2392]

Did you manage to get this ?

[@divyaverma1101]

It didn't worked,,, even though I followed exactly same steps.🙄