Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

Story point calculation query

Neeta Dubey
Contributor
April 15, 2025

Hi Team,

I've written automation rule to sum story points of subtask and show it on the story however while doing calculation on the board this is creating issues.

Ideally Story point total is 1 week now and so estimated should also appear as 1 w however it doing the calcuation like 2w=[1w + 3d +1d +1dsp.png

2 answers

0 votes
Rudy Holtkamp
Community Champion
April 15, 2025

As a suggestion you could use a rule that looks something like this:

image.png

Here I place a comment in the parent, but you could also update a field in the parent.

Neeta Dubey
Contributor
April 15, 2025

hi Rudy,

 

Thank you so much for looking into this. Here is the screen shot.

rule_s.png

Rudy Holtkamp
Community Champion
April 16, 2025

No problem, @Neeta Dubey ,

Correct me if I'm wrong.

What you want is to sum all original estimates of the subtasks and put that sum in the original estimate of the parent of these subtasks. 

First of all, there are two values which make up the field 'time tracking'. That is the original estimate and the remaining estimate. The first time you write a value into the original estimate, it will be copied to the remaining estimate. In fact as long as you don't log work (change the remaining estimate) changes to the original estimate will be copied.

Next, as a concept, estimation is first done on larger chunks of work, later it is more refined when you split up that work into smaller pieces which can be better estimated. (Initiative > Epic > story > sub-tasks) . This means that your original estimation of the task should remain what it was. And when you create subtasks and start estimating these, you would copy remaining estimates of the children (which is initially the same as the original estimate) to the remaining estimate of the parent.

With this concept you see what the difference with your original estimation.

--

When I take a look at your automation rule I don't find any big problems. 

I would prefer to use 'Field value changed' for the Time tracking field instead of Update issue, because it will reduce the number of times the automation rule is triggered.

Then I would use this as smart value:

{{#=}}{{issue.subtasks.timeoriginalestimate.sum}}/60{{/}}m

The m is for minutes.

But I don't see why is would add two weeks instead of one. Since you are overwriting the original estimate of the parent with the summation of the original estimates of the children (3d+1d+1d)

0 votes
Neeta Dubey
Contributor
April 15, 2025

sp.png

Rudy Holtkamp
Community Champion
April 15, 2025

Hi @Neeta Dubey ,

Could you post your automation rule? It will be easier to zoom in what is going on/wrong.

Kind regards,

Rudy

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
ENTERPRISE
TAGS
AUG Leaders

Atlassian Community Events