How to sum up story point of all the subtasks together with the story points of the Parent

[lusine.abrahamyan@disqo.com]

Currently I have set up sum-up automation rule for sub-task using:

{{subtasks.Story Points.join(" + ")}}

which works well for the subtasks SPs. So if:

Sub-task 1 = 3

Sub-task2 = 2

The Parent story point = 5 which is fine. But I also want to have the sum of SPs for the parent issue+sub-tasks. In other words, I need the following:

Sub-task 1 = 3

Sub-task2 = 2

Story = 3

The total Story Points of the Story to equal 8

Which query should I use in this case? Using the above mentioned query doesn't work.

Thanks for help

[Bill Sheboy]

Hi lusine.abrahamyan@disqo.com -- Welcome to the Atlassian Community!

What problem are you trying to solve by doing this, as some of what you describe seems confusing to me?

When teams use Stories and Subtasks together, the Subtasks are the child items to delivery the Story.  That is, they are a work-breakdown list for all of the work to delivery it.  There is no remaining work...if there was then there are missing Subtasks to add.

This is also why Stories may have a sizing of Story Points and the Subtasks do not.  So your idea of both having sizes seems to indicate there are missing Subtasks or double-accounting of the sizing.

Thanks, and kind regards,
Bill

[lusine.abrahamyan@disqo.com]

Hi @Bill Sheboy

Nice to meet you.

There are no missing subtasks. And subtasks are aways estimated. Let me clarify:

Assume we have a Story and 2 sub-tasks.

Story has Assignee 1

Sub-task 1 has Assignee 2

Sub-task 2 has Assignee 3

For some logical reasons we also have assignee for the Story. And we have the following estimations:

Sub-task 1 =3

Sub-task 2 = 2

And the Story is separately estimated = 3

If the Story is not separately estimated it get the sum-up of the sub-tasks, i.e. 5 SP, which is fine. The query used is {{subtasks.Story Points.join(" + ")}}

I want to know if there is a query that will add sub-tasks SPs to the Story's SP, ie:

3+2+3=8

In my former Company we used time estimations and when we were estimating separately the Story and the Sub-tasks, we were getting no duplications but the sum of the 3 tickets. That's why I know that it's possible.

[Bill Sheboy]

Thanks for that information, and...

It would appear there is work for the Story separate from the child Subtasks...which is why I considered that to be other work that is missing a Subtask.

To do what you describe with story points, you would need a separate custom field for the total story points, although none of the built-in functions for reporting will work with that field: velocity, burn charts, etc.

[lusine.abrahamyan@disqo.com]

No need for a custom field. The following smart value solves the problem: {{triggerissue.Story Points}} + {{issue.Story Points}}