AutoSum sub items

[Klaas van der Hoeven]

Hi there, 
My question about the auto sum function of storypoints in sub-items remaind unsolved.

Maybe I can show you my settings. Is there a solution why Jora does not sum the storypoints from teh sub issues to the parent issues?

I renamed the sub issues to 'onderliggende items', that is Duch :)
Maybe that is the problem?

[Pramodh M]

Hi @Klaas van der Hoeven 

It does not automatically sum up the story points to Story Issue.

We need to create an Automation rule in order to sum up the story points of all the sub-tasks to the parent issue

Here is guide on how to do that

https://community.atlassian.com/t5/Automation-discussions/Jira-Automation-Complete-Video-Guides-on-how-to-Sum-Up-Story/m-p/1741948#M75

Let me know if you have queries

Thanks,
Pramodh

[Nic Brough -Adaptavist-]

Jira does not add story points from sub-tasks up into their parent issues because it breaks your reporting.

Sub-tasks are a part of their parent story, not a separate entity and, most importantly, they are not items you commit to in a sprint.  As they are not sprint items, they do not have sprint estimates.  Their sprint estimate is part of the sprint-able items of which they are a part.

There are strategies people can impose that enable sprint estimates to be useful on sub-tasks, but Jira does not implement any of them, it goes with the most simple case of "do not put sprint estimates on sub-tasks"

So, that's the "why it doesn't add them up" off-the-shelf.  

You can of course automate something to do it.  Or you could just stop trying to do scrum, or choose to ignore the sprint reporting and velocity.

I would very strongly recommend that you do not just implement a script or automation that adds up sprint estimates on to stories.  Your sprint reports (velocity) will not recognise them, and your other reporting will double-count them.  It's going to go wrong for everything. 

If you want to do scrum while putting sprint estimates such as story points on sub-tasks then build a proper strategy for doing it (essentially, you need to have two estimate fields, one for the estimate you put on sub-tasks, and another for the stories which takes account of the estimates on the sub-tasks somehow, and can be used as the scrum estimation field)